# proofite (slim) > proofite, an MCP server by proofite.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Read your AI-written daily briefing and retune the filter behind it: feeds, newsletters, topics. - Full: https://www.anchorterminal.com/tools/proofite.md (~1,900 tokens) · this version ~1,830 tokens · JSON https://www.anchorterminal.com/tools/proofite.json · canonical https://www.anchorterminal.com/tools/proofite - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-05 # proofite > Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/ - Kind: MCP server, by proofite.com (https://proofite.com/mcp) - Category: Data providers (https://www.anchorterminal.com/categories/data-providers.md) - Listed because: It's published in the registry under proofite.com, a namespace the registry only gives to whoever proves they control that domain. - What the official MCP registry says: 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 (streamable HTTP) - Package: npm `proofite-mcp` (stdio) - Source: https://github.com/hanicker/proofite-mcp - Website: https://proofite.com/mcp - npm downloads a week: 31 - GitHub stars: 0 - Registry entry updated: 2026-08-17 ## Tools - Tools it lists (28, about 5,772 tokens of context, `tools/list` without credentials over MCP 2026-07-28, checked 2026-10-04 22:23 UTC): - `get_briefing` (read-only): 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… - `list_briefings` (read-only): 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… - `get_information_diet` (read-only): Read everything that shapes what reaches this person: delivery schedule, length, technicality, depth, stance and tone, stated interests and no-go topics, the… - `list_sources` (read-only): 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… - `get_source` (read-only): 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… - `get_podcast_episode` (read-only): 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… - `list_read_later` (read-only): List what is queued in the read-later inbox: links and forwarded emails that are guaranteed to be covered in the next briefing. - `list_deep_dives` (read-only): List the deep-dive research requests waiting to be covered: topics the user asked the briefing to investigate with fresh web research. - `get_account` (read-only): 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… - `update_information_diet` (writes): Change how and when the briefing reaches this person: delivery time and days, length, technicality, depth, stance, tone, stated interests and topics to avoid,… - `tune_topic` (writes): 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… - `correct_briefing` (writes): 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… - `rate_briefing_entry` (writes): 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… - `report_missing_story` (writes): 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… - `set_learned_profile` (writes): 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.… - `request_deep_dive` (writes): 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… - `save_for_later` (writes): 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,… - `generate_briefing` (writes): 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… - `create_source` (writes): 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… - `update_source` (writes): 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… - `delete_source` (writes): Permanently delete a topic inbox with all its feeds, searches and collected content. Irreversible: the dedicated email address stops working too. Prefer… - `add_feed` (writes): 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,… - `remove_feed` (writes): Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it. - `add_web_search` (writes): 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… - `remove_web_search` (writes): Stop monitoring a standing web search: no new results from that query will reach the briefing. What it already collected stays where it is. - `discover_sources` (read-only): 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… - `import_opml` (writes): Import subscriptions from another RSS reader (Feedly, Inoreader, FreshRSS, NetNewsWire) by passing the OPML file contents. Set dry_run true first to see what… - `unsubscribe_newsletter` (writes): 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… - How its tools read to an agent (0 errors, 0 warnings, 1 note, about 5,772 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score): - note TC24 server: 28 of 28 tools have no outputSchema - JSON: https://www.anchorterminal.com/api/v1/tools/proofite.json - Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming