proofite by proofite.com
MCP server · Data providers · indexed, not reviewed
HostedLocalvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Read your AI-written daily briefing and retune the filter behind it: feeds, newsletters, topics.
Facts
- MCP registry
com.proofite/proofite· 1.0.0- Endpoint
https://proofite.com/mcp- Packages
npmproofite-mcp stdio- Website
- proofite.com/mcp
- npm / week
- 31
- GitHub stars
- 0
- Registry entry
- updated 17 Aug 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under proofite.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 28 · about 5,772 tokens of context · checked 13 minutes ago
| Tool | What it does | Hint |
|---|---|---|
get_briefingRead the daily briefing | Read the user's personal AI-written news briefing (daily digest) in full markdown: every story selected today from their newsletters, RSS feeds and monitored web searches, with sources. Returns the latest briefing by… | read-only |
list_briefingsList past briefings | List the user's past daily briefings (most recent first) with date, title, number of stories and whether an episode exists. Use it to find the id of a specific day before reading or correcting it. | read-only |
get_information_dietRead the information diet | Read everything that shapes what reaches this person: delivery schedule, length, technicality, depth, stance and tone, stated interests and no-go topics, the profile the system has learned about them, the per-topic… | read-only |
list_sourcesList information sources | List the topic inboxes this person feeds their briefing with: each one has a dedicated email address for newsletter subscriptions, plus RSS feeds and monitored web searches. Shows how much each produced recently, its… | read-only |
get_sourceInspect one source | Inspect one topic inbox in detail: every RSS feed (with its health and last fetch), every monitored web search, X/Twitter profiles, and the newsletters currently arriving at its dedicated address. Use it before removing… | read-only |
get_podcast_episodeGet the podcast episode | Get the audio episode generated from a briefing: a private podcast narrated in the user's language, with a playable URL and the show notes listing every source. Returns the latest episode by default. | read-only |
list_read_laterList the read-later queue | List what is queued in the read-later inbox: links and forwarded emails that are guaranteed to be covered in the next briefing. | read-only |
list_deep_divesList pending deep dives | List the deep-dive research requests waiting to be covered: topics the user asked the briefing to investigate with fresh web research. | read-only |
get_accountAccount and usage | Account status: plan, whether the briefing is currently running, when the next one is due, how many sources and stories are in the system, and the AI cost accrued this month. | read-only |
update_information_dietChange how the briefing is written | Change how and when the briefing reaches this person: delivery time and days, length, technicality, depth, stance, tone, stated interests and topics to avoid, language, timezone, podcast and email delivery. Pass only… | writes |
tune_topicTune one topic | Tune how a single topic is treated in future briefings: more or less of it, more or less technical, deeper or shorter, more or less often, muted entirely, or followed so every development of that WHOLE THEME gets… | writes |
correct_briefingCorrect the briefing in plain words | Tell the briefing what was wrong with it, in plain language — "too much crypto and not enough on the EU regulation", "keep it shorter", "explain the technical parts more simply", "follow this story". An AI editor reads… | writes |
rate_briefing_entryRate one story | Give a precise up/down signal on one story of a briefing: more like this, less like this, more technical, simpler, deeper, shorter, or mute its topics. These apply to the topics of that story, so the next briefing… | writes |
report_missing_storyAsk why a story was missing | The reader expected a story and the briefing did not have it. Describe it in their words; the editor investigates their own sources of the last days, today's briefing, their preferences and a web search, and answers… | writes |
set_learned_profileRewrite the learned profile | Read or rewrite the free-text profile the briefing uses to know who this person is — their work, projects, recurring interests, what they already know. Appending is usually better than replacing: pass mode "append" to… | writes |
request_deep_diveQueue a deep dive | Ask the next briefing to investigate a topic properly, with fresh web research: it will include a mini-dossier with sources. Use it whenever the person says "I want to know more about X" or "keep digging on this". | writes |
save_for_laterSave something into the next briefing | Put a link or a note into the read-later queue: whatever lands there is guaranteed to be covered in the next briefing. The page is fetched and its text stored, so it can be summarised even if the site later blocks… | writes |
generate_briefingGenerate a briefing now | Generate a briefing immediately instead of waiting for the scheduled time, using everything collected so far. Costs real AI money and takes a couple of minutes, so use it only when explicitly asked. Returns the id to… | writes |
create_sourceCreate a topic inbox | Create a new topic inbox: a themed container with its own dedicated email address (subscribe newsletters to it), which can hold RSS feeds and monitored web searches. This is how you add a whole new subject to someone's… | writes |
update_sourceUpdate a topic inbox | Change a topic inbox: rename it, change its description, raise or lower its priority in the briefing, set a per-inbox technicality level, temporarily exclude it from the briefing or pause it entirely. | writes |
delete_sourceDelete a topic inbox | Permanently delete a topic inbox with all its feeds, searches and collected content. Irreversible: the dedicated email address stops working too. Prefer update_source with is_active false when in doubt. | writes |
add_feedAdd an RSS feed | Add an RSS/Atom feed to a topic inbox. You can pass the site address instead of the feed URL — the server fetches the page and discovers the feed. If it fails, the reason is precise (blocked by the site, gone,… | writes |
remove_feedRemove an RSS feed | Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it. | writes |
add_web_searchMonitor a web search | Monitor a Google query every day and feed the results into a topic inbox: the standing-search way to follow a company, a person, a law or a niche subject that has no RSS feed. kind "news" watches the news index,… | writes |
remove_web_searchStop monitoring a search | Stop monitoring a standing web search: no new results from that query will reach the briefing. What it already collected stays where it is. | writes |
discover_sourcesFind sources for a subject | Describe a subject in plain words and get back real, working sources for it: RSS feeds validated live by the server (dead ones are dropped before you see them), web searches worth monitoring, and newsletters worth… | read-only |
import_opmlImport an OPML subscription file | Import subscriptions from another RSS reader (Feedly, Inoreader, FreshRSS, NetNewsWire) by passing the OPML file contents. Set dry_run true first to see what is in it and what is already present; then run it for real to… | writes |
unsubscribe_newsletterUnsubscribe from a newsletter | Unsubscribe from a newsletter arriving in one of the inboxes. When the sender supports one-click unsubscribe the server does it directly; otherwise it returns the URL a human has to open, and says so honestly. | writes |
What https://proofite.com/mcp answered to tools/list, asked without credentials over MCP 2026-07-28. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 0 warnings · 1 note
- noteTC24server28 of 28 tools have no outputSchema
The checks from /check and anchor check, run each day on the list above: about 5,772 tokens of definitions. Not part of the score yet. Check your own server.