MCP servercom.proofite/proofite
Read your AI-written daily briefing and retune the filter behind it: feeds, newsletters, topics.
Overview
Score?
UNRATED 0.820
of what a free look can see, on 33 looks
Looks
36
last 6 hr ago
Tools
28
changed 16 days ago
More info
URL
proofite.com/mcp
streamable-http
Says it is
proofite 1.0.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.820 · highest on record 0.8561
Toolsfrom sha256:eca95e5d68…19c4bd · +0 −0 16 days ago
| Tool | Schema |
|---|---|
| add_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 precis |
input · no output |
| add_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 |
input · no output |
| correct_briefing 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", " |
input · no output |
| create_source 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 yo |
input · no output |
| delete_source 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_activ |
input · no output |
| discover_sources 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 |
input · no output |
| generate_briefing 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 |
input · no output |
| get_account 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. |
input · no output |
| get_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 sou |
input · no output |
| get_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 |
input · no output |
| get_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 |
input · no output |
| get_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 de |
input · no output |
| import_opml 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 a |
input · no output |
| list_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 o |
input · no output |
| list_deep_dives List the deep-dive research requests waiting to be covered: topics the user asked the briefing to investigate with fresh web research. |
input · no output |
| list_read_later List what is queued in the read-later inbox: links and forwarded emails that are guaranteed to be covered in the next briefing. |
input · no output |
| list_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 |
input · no output |
| rate_briefing_entry 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 |
input · no output |
| remove_feed Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it. |
input · no output |
| remove_web_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. |
input · no output |
| report_missing_story 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 prefer |
input · no output |
| request_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 ab |
input · no output |
| save_for_later 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 summari |
input · no output |
| set_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 |
input · no output |
| tune_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 deve |
input · no output |
| unsubscribe_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 t |
input · no output |
| update_information_diet 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, p |
input · no output |
| update_source 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 o |
input · no output |
Verify it yourself
npx teppi-check https://proofite.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ28EK3BW36RX3HC29S0AP