Skip to main content

proofite

com.proofite/proofiteVersion 1.2.0

Read your AI-written daily briefing and retune the filter behind it: feeds, newsletters, topics.

Status

Responds158 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 14:11 UTC
Latency
158 ms
Remotes responding
1 of 1
Sign-in
API key
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://proofite.com/mcpResponds158 ms
No sign-in

Claude Code

claude mcp add --transport http proofite https://proofite.com/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'

Replace <YOUR_TOKEN> before running.

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: proofite
Remote MCP server URL: https://proofite.com/mcp
This server expects the header Authorization.

Cursor

{
  "mcpServers": {
    "proofite": {
      "url": "https://proofite.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Replace <YOUR_TOKEN> before running.

VS Code

code --add-mcp '{"name":"proofite","type":"http","url":"https://proofite.com/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'

Replace <YOUR_TOKEN> before running.

Streamable HTTP
npm: proofite-mcp 1.2.0
Package only

npm (npx)

claude mcp add proofite -e 'PROOFITE_API_KEY=<YOUR_PROOFITE_API_KEY>' -- npx -y proofite-mcp@1.2.0

Replace <YOUR_PROOFITE_API_KEY> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

47 tools

Tools of proofite
Read-only
Idempotent
Open world
add_feedAdd 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. A podcast works too (its feed, its site, or an Apple Podcasts or Spotify link): it is followed as a podcast, and every new episode is transcribed and enters the briefing. If it fails, the reason is precise (blocked by the site, gone, unreadable) so it can be reported honestly.NoNoYesYes
add_proposed_sourceWhen report_missing_story found that none of the person's sources carried the story, it proposed one. This adds that proposed feed to the inbox it indicated — the same tap the reader has under the briefing. Idempotent: adding twice says it was already added.NoNoYesYes
add_web_searchMonitor 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, "search" the whole web.NoNoYesYes
cancel_deep_diveRemove a deep-dive request that is still waiting (ids from list_deep_dives). One already covered in a briefing cannot be cancelled.YesNoYesNo
configure_insertConfigure one insert of the briefing. Call list_inserts first: it returns, for each insert available to this person (language and country already applied), the config fields with their key, type and options. Pass the insert id and any subset of: enabled (true/false), level (one of the insert's AI levels: nessuno = data only, leggero = the podcast hosts mention it, medio = plus a short written comment), config (an object keyed by the field keys). Field types: "luoghi" takes city names as strings (e.g. {"citta": ["Verona"]}; resolved to coordinates here), "lista_testo" takes an array of strings or the pasted text under "<key>_testo", "titoli"/"squadra" take names as strings, "scelta" takes one option id, "scelta_multipla" an array of option ids, "testo" a string. Examples: meteo {"citta": ["Verona", "Milano"], "orizzonte": "weekend"}; fantacalcio {"rosa": ["Contini", "Milinkovic-Savic V."], "lega": "…"}; borsa {"titoli": ["Enel", "Nvidia"]}; rebus {"livello_gioco": "facile", "quando": "weekend"}. Switching on requires a valid configuration. Takes effect from the next briefing.NoNoYesNo
correct_briefingTell 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". An AI editor reads the note against the actual briefing and turns it into concrete adjustments: topic preferences, settings (technicality, depth, length, podcast minutes, tone), deep-dive requests. This is the main way a person retunes their news feed by talking. To pin ONE story so its developments get reported, pass its entry_id with the note, or use rate_briefing_entry with "follow": a note without entry_id can only follow a whole theme.NoNoNoNo
create_sourceCreate 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 information diet.NoNoNoNo
delete_sourcePermanently 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.YesNoYesNo
discover_sourcesDescribe 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 subscribing to. Nothing is added — it returns proposals to pass to add_feed / add_web_search.Not declaredYesNot declaredYes
generate_briefingGenerate 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 poll with get_briefing.NoNoNoNo
generate_podcast_episodeMake (or remake) the podcast episode of a briefing right away — the latest by default. Takes a few minutes (script, then voices); poll with get_podcast_episode. Asking for an episode is a listening signal: it also lifts the automatic pause. Costs real AI money, so only when asked.NoNoNoNo
get_accountAccount 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.Not declaredYesNot declaredNo
get_briefingRead 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 default, or a specific one by id or date. Also returns an index of entry ids, needed to rate or correct individual stories.Not declaredYesNot declaredNo
get_episode_transcriptThe full text of a podcast episode, word for word: the script the voices read. In the two-host show it comes as "Name: line" turns; in the classic format as plain paragraphs. Use it when the person wants a passage quoted, a point the hosts made that the written briefing does not have, or to search what was said. Latest episode by default.Not declaredYesNot declaredNo
get_information_dietRead everything that shapes what reaches this person: delivery schedule, length, technicality, depth, stance, tone and entry mix, podcast format (two-host show or single voice), voice accent and whether the podcast is auto-paused, stated interests and no-go topics, the profile the system has learned about them, the per-topic preferences built from their feedback (affinity, muted, followed themes) and the specific stories they pinned with "follow" (every development of those gets reported). This is the full picture of their news filter — read it before changing anything.Not declaredYesNot declaredNo
get_insertEverything about ONE insert (an optional extra page of the briefing; the list is in list_inserts), in the person's language: what it does and how it works, how often it shows up and where it sits in the briefing, its short guide, its data sources, the AI levels it offers, every configuration field with its options and its current value, and this person's state: on or off, configured or not, the level, the configuration summed up in a phrase, the link that opens it in the app. Use it to explain an insert or to prepare configure_insert.Not declaredYesNot declaredNo
get_page_helpGiven a page of the Proofite app (the path from the address bar, like /app/digests, /app/edicola, /app/settings, or a full link), says what that page is, what can be done there and which features live on it, with their state for this person; on a briefing or an inbox it also says which one. Use it when the person asks "what is this?", "what can I do here?" or "where do I find X?" about the screen in front of them. The texts are in Italian, the language the app is written in: say them in the person's language. An unknown path gets the list of the pages that exist.Not declaredYesNot declaredNo
get_podcast_episodeGet the audio episode generated from a briefing: a private podcast in the user's language — by default a show with two hosts who talk the news through, or a single voice in the classic format — with a playable URL, the private RSS feed URL and the show notes listing every source. Returns the latest episode by default. For the words themselves use get_episode_transcript.Not declaredYesNot declaredNo
get_sourceInspect 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 or reorganising anything.Not declaredYesNot declaredNo
import_opmlImport 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 add them (they are validated one by one, and the ones that fail come back with the reason).NoNoYesYes
list_briefingsList 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.Not declaredYesNot declaredNo
list_deep_divesList the deep-dive research requests waiting to be covered: topics the user asked the briefing to investigate with fresh web research.Not declaredYesNot declaredNo
list_featuresWhat Proofite can do for this person, feature by feature and grouped by family (reading, listening, correcting, sharing…): for each feature a short explanation, its state for THIS account (on; off, with the setting that switches it on; or "not yet", with what has to happen first), a personal example from their own numbers when there is one, and the page of the app where it lives. Use it to answer "what can I do with Proofite?", "is X on?" or "why don't I see X?" before changing anything. The texts are in Italian, the language the app is written in: say them in the person's language. Settings change with update_information_diet, inserts with configure_insert.Not declaredYesNot declaredNo
list_insertsThe inserts: optional extra pages of the daily briefing that the person switches on one by one — weather for their city, their fantasy-football roster (Italian users), the stocks they hold, a daily rebus puzzle. Returns, in the person's language, each insert with what it does, whether it is on, its current configuration, the fields it needs (with types) and the AI levels it offers. Read this before configure_insert.Not declaredYesNot declaredNo
list_missing_reportsThe investigations opened with report_missing_story on a briefing: what was asked, the verdict, the explanation, the signals applied and — when none of the person's sources carried the story — the source proposed, with whether it was already added. Latest briefing by default.Not declaredYesNot declaredNo
list_read_laterList what is queued in the read-later inbox: links and forwarded emails that are guaranteed to be covered in the next briefing, and — apart — the stories the person deferred to a later day ("snoozed"), which wait until their date.Not declaredYesNot declaredNo
list_savedThe reading list: stories the person saved from their briefings (including the "chicca", the archive story of quiet days), newest first, each with the briefing it came from. Pass `query` to search them by any word — title, text, topics, briefing title. To add or remove: save_entry, unsave_entry.Not declaredYesNot declaredNo
list_sourcesList 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 priority and whether it is included in the briefing.Not declaredYesNot declaredNo
rate_briefing_entryGive a precise up/down signal on one story of a briefing: more like this, less like this, more technical, simpler, deeper, shorter, or mute. A story carries typed labels (see `labels` in get_briefing): e:<who or what> (e:tesla), c:<field, its world> (c:auto), f:<angle> (f:soldi = money) and free tags. `topics` chooses the LEVEL: one label = broad ("less of Tesla, everywhere"); several labels = narrow, they are COMBINED with AND ("less of Tesla + soldi" = Tesla only when the story is about money; Tesla alone and money stories of others are untouched). Omit `topics` for the whole story (all its labels together, the narrowest level). Sending the same signal again with different topics REPLACES the previous one. "follow" is different: it pins THIS story — every development of it (and only of it) gets a full entry; "unfollow" releases it. `withdraw: true` takes a signal back.NoNoNoNo
rate_insertLeave feedback on one insert of the briefing for the people who build it: stars from 1 to 5 and/or a comment of up to 1000 characters, at least one of the two. Use it when the person judges an insert — "the weather page is great", "the quiz is too hard", "the stocks insert is missing my bank" — passing the insert id (see list_inserts), the stars if they gave a grade, and the comment in their own words. A second call within fifteen minutes completes or corrects the same feedback instead of adding another; later calls add a new one. Comments reach the founder; stars are read in aggregate. Returns the current average for that insert.NoNoNoNo
remove_feedRemove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it.YesNoYesNo
remove_web_searchStop monitoring a standing web search: no new results from that query will reach the briefing. What it already collected stays where it is.YesNoYesNo
report_missing_storyThe 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 with a verdict: it was in the briefing, none of their sources carried it (and proposes the missing source), it was dropped because of a preference (and corrects it), it was seen but undervalued, or it could not be found. Topics get followed so similar stories do not slip again; a deep-dive may be queued for the next briefing. Five per day.NoNoNoYes
request_deep_diveAsk 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".NoNoYesNo
resume_podcastThe podcast pauses itself when nobody listens for a while (no episodes get made; the setting podcast_enabled stays true). This lifts the pause: from tomorrow the episode comes back every morning. get_information_diet and get_account say whether it is paused.NoNoYesNo
save_entryKeep one story of a briefing in the reading list (list_saved): a snapshot that survives even if the briefing is deleted. entry_id "chicca" saves the chicca — the archive story of quiet days — when the briefing has one. Saving again only refreshes the date.NoNoYesNo
save_for_laterPut 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 access.NoNoYesYes
search_briefingsSearch the person's past daily briefings for a word or a phrase, in the titles and in the text of every story, newest first. Each result has the briefing id, date and title, the passage around the match and, when the match is inside a story, that story's entry id and headline, with the link that opens the briefing right there. Use it for "when did you tell me about X?" or "find that piece on Y", then read the briefing with get_briefing. The match is literal, with no synonyms: if nothing comes back, try a shorter word or another spelling. The reading list has its own search (list_saved).Not declaredYesNot declaredNo
set_learned_profileRead 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 add a line.YesNoNoNo
share_briefingCreate (or read) the public link of a briefing: a cleaned-up read-only copy — no personal "why this matters to you" notes, no name. The podcast episode comes along only if `podcast` is true: the hosts greet the reader by name, so that is the reader's call. Idempotent: calling again returns the same link; unshare_briefing revokes it.NoNoYesNo
tune_topicTune how a single topic — or a COMBINATION of labels — 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 reported (to follow one specific story, use rate_briefing_entry with "follow" on that entry). `topic` is one key: a free tag ("intelligenza artificiale") or a typed label (e:tesla, c:auto, f:soldi); `topics` instead is a list of labels combined with AND ("e:tesla"+"f:soldi" = Tesla only when about money — Tesla alone stays as it is). This is the precise instrument — for a vague comment like "too much crypto lately" use correct_briefing instead.NoNoNoNo
unfollow_storyRelease a pinned story by its id (from get_information_diet → followed_stories), so its developments stop getting a dedicated entry. Works even when the briefing it came from is gone — rate_briefing_entry "unfollow" needs the briefing, this does not.NoNoYesNo
unsave_entryTake a story out of the reading list, by its saved id (from list_saved) or by briefing + entry id.YesNoYesNo
unshare_briefingRevoke the public link of a briefing: the page and its audio stop answering immediately.YesNoYesNo
unsubscribe_newsletterUnsubscribe 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.YesNoYesYes
update_information_dietChange how and when the briefing reaches this person: delivery time and days, length, technicality, depth, stance, tone, entry mix (few deep stories vs many short ones), stated interests and topics to avoid, language, timezone; the podcast (on/off, minutes, two-host show or single voice, voice accent), email delivery, the weekly recap, the chicca on quiet days, the smalltalking stories, web enrichment. Pass only the keys you want to change. Read get_information_diet first — these are global settings, not per-topic ones (for a single topic use tune_topic).NoNoYesNo
update_sourceChange 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.NoNoYesNo

Details

Registry status
Active
Published
Oct 6, 2026
Updated
Oct 6, 2026
Categories (suggested)
Search and webSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing