com.proofite/proofite

Official40 tools

by hanicker · JavaScript

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

Proofite MCP Server (com.proofite/proofite)

This Model Context Protocol (MCP) server enables AI agents to read Proofite’s AI-written daily briefing and to retune the filtering settings that control that briefing. It connects to selected sources such as newsletters and RSS feeds and is used by Proofite’s own voice mode.

🛠️ Key Features

Read a daily briefing generated by AI
Retune the filter behind the briefing
Control what gets in, including depth and technicality
Adjust how often content appears and what never appears again
Supports sources like newsletters, RSS feeds, monitored web searches, and saved links
Available as a podcast via Proofite

🚀 Use Cases

Agents that need morning briefing context
Updating information diet preferences (frequency, depth, technical level)
Preventing repeated topics from appearing in future briefings

⚡ Developer Benefits

Lets agents access the same briefing used in Proofite
Enables programmatic control of briefing filtering behavior
Built as the actual server used by the product’s voice mode

⚠️ Limitations

The provided description does not list specific MCP tools, schemas, or authentication details.

Topics

agentaiclaudemcpmcp-servermodel-context-protocolnewsnewsletterpodcastrss

Captured live from the server via tools/list.

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 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.

Parameters2

briefing_id	string	optional	Specific briefing id (from list_briefings). Omit for the latest.
include_markdown	boolean	optional	Include the full text. Default true; set false for just the index.

Raw schema

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Specific briefing id (from list_briefings). Omit for the latest."
    },
    "include_markdown": {
      "type": "boolean",
      "description": "Include the full text. Default true; set false for just the index."
    }
  },
  "additionalProperties": false
}

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 or correcting it.

Parameters2

limit	integer	optional	How many, default 10
offset	integer	optional	Skip the N most recent: use it to walk back through an archive longer than 50 (default 0)

Raw schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "How many, default 10"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip the N most recent: use it to walk back through an archive longer than 50 (default 0)"
    }
  },
  "additionalProperties": false
}

get_information_diet

Read 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.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

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 how much each produced recently, its priority and whether it is included in the briefing.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

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 dedicated address. Use it before removing or reorganising anything.

Parameters1

source_id

string

required

Id from list_sources

Raw schema

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Id from list_sources"
    }
  },
  "required": [
    "source_id"
  ],
  "additionalProperties": false
}

get_podcast_episode

Get 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.

Parameters1

briefing_id

string

optional

Episode of a specific briefing. Omit for the latest.

Raw schema

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Episode of a specific briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}

get_episode_transcript

The 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.

Parameters2

briefing_id	string	optional	The episode of a specific briefing. Omit for the latest.
episode_id	string	optional	A specific episode (from get_podcast_episode). Wins over briefing_id.

Raw schema

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "The episode of a specific briefing. Omit for the latest."
    },
    "episode_id": {
      "type": "string",
      "description": "A specific episode (from get_podcast_episode). Wins over briefing_id."
    }
  },
  "additionalProperties": false
}

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, and — apart — the stories the person deferred to a later day ("snoozed"), which wait until their date.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

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.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

list_saved

The 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.

Parameters2

query	string	optional	Optional: a word to search for
limit	integer	optional	How many to return (default 30)

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional: a word to search for"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "How many to return (default 30)"
    }
  },
  "additionalProperties": false
}

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.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

update_information_diet

Change 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).

Parameters22

digest_enabled	boolean	optional	ricevere o meno il briefing quotidiano
digest_time	string	optional	orario di consegna, HH:MM nel fuso dell'utente
digest_days	array	optional	giorni della settimana, ISO 1=lunedì … 7=domenica
digest_length	string	optional	quanto deve essere lungo
technicality	integer	optional	1 divulgativo … 5 da addetti ai lavori
depth	integer	optional	1 solo i fatti … 5 analisi e implicazioni
entry_mix	integer	optional	1 poche voci trattate a fondo … 5 tante voci brevi (la lunghezza totale non cambia)
stance	integer	optional	1 neutro … 5 l'editor si sbilancia
tone	string	optional	come deve scrivere («diretto, zero fuffa»)
interests	string	optional	cosa seguire, in linguaggio naturale
avoid	string	optional	cosa non vuole leggere mai
language	string	optional	lingua del briefing e del podcast
timezone	string	optional	fuso orario IANA (Europe/Rome)
podcast_enabled	boolean	optional	generare anche l'episodio audio
podcast_minutes	integer	optional	durata desiderata dell'episodio
podcast_formato	string	optional	show = due conduttori che si rispondono (il formato di casa); classico = una voce che legge il briefing
podcast_accento	string \| null	optional	accento della voce, per la lingua scelta: inglese us/gb/au/ie/in, spagnolo es/latam, francese fr/ca, tedesco de/at/ch (l'italiano non ha varianti); null = automatico, abbinato alla lingua
email_digest_enabled	boolean	optional	ricevere il briefing anche per email
weekly_recap_enabled	boolean	optional	riepilogo settimanale di ciò che non è stato letto
chicca_enabled	boolean	optional	nei giorni senza notizie, una storia vera dall'archivio
smalltalking_enabled	boolean	optional	ogni giorno, in coda al briefing, due o tre storie brevi da raccontare
serper_enrich	boolean	optional	arricchire il briefing con ricerche web fresche

Raw schema

{
  "type": "object",
  "properties": {
    "digest_enabled": {
      "description": "ricevere o meno il briefing quotidiano",
      "type": "boolean"
    },
    "digest_time": {
      "description": "orario di consegna, HH:MM nel fuso dell'utente",
      "type": "string"
    },
    "digest_days": {
      "description": "giorni della settimana, ISO 1=lunedì … 7=domenica",
      "type": "array",
      "items": {
        "type": "integer",
        "minimum": 1,
        "maximum": 7
      }
    },
    "digest_length": {
      "description": "quanto deve essere lungo",
      "type": "string",
      "enum": [
        "short",
        "medium",
        "long",
        "xlong",
        "full"
      ]
    },
    "technicality": {
      "description": "1 divulgativo … 5 da addetti ai lavori",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "depth": {
      "description": "1 solo i fatti … 5 analisi e implicazioni",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "entry_mix": {
      "description": "1 poche voci trattate a fondo … 5 tante voci brevi (la lunghezza totale non cambia)",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "stance": {
      "description": "1 neutro … 5 l'editor si sbilancia",
      "type": "integer",
      "minimum": 1,
      "maximum": 5
    },
    "tone": {
      "description": "come deve scrivere («diretto, zero fuffa»)",
      "type": "string"
    },
    "interests": {
      "description": "cosa seguire, in linguaggio naturale",
      "type": "string"
    },
    "avoid": {
      "description": "cosa non vuole leggere mai",
      "type": "string"
    },
    "language": {
      "description": "lingua del briefing e del podcast",
      "type": "string",
      "enum": [
        "it",
        "en",
        "es",
        "de",
        "fr"
      ]
    },
    "timezone": {
      "description": "fuso orario IANA (Europe/Rome)",
      "type": "string"
    },
    "podcast_enabled": {
      "description": "generare anche l'episodio audio",
      "type": "boolean"
    },
    "podcast_minutes": {
      "description": "durata desiderata dell'episodio",
      "type": "integer",
      "minimum": 2,
      "maximum": 20
    },
    "podcast_formato": {
      "description": "show = due conduttori che si rispondono (il formato di casa); classico = una voce che legge il briefing",
      "type": "string",
      "enum": [
        "show",
        "classico"
      ]
    },
    "podcast_accento": {
      "description": "accento della voce, per la lingua scelta: inglese us/gb/au/ie/in, spagnolo es/latam, francese fr/ca, tedesco de/at/ch (l'italiano non ha varianti); null = automatico, abbinato alla lingua",
      "type": [
        "string",
        "null"
      ],
      "enum": [
        "us",
        "gb",
        "au",
        "ie",
        "in",
        "es",
        "latam",
        "fr",
        "ca",
        "de",
        "at",
        "ch",
        null
      ]
    },
    "email_digest_enabled": {
      "description": "ricevere il briefing anche per email",
      "type": "boolean"
    },
    "weekly_recap_enabled": {
      "description": "riepilogo settimanale di ciò che non è stato letto",
      "type": "boolean"
    },
    "chicca_enabled": {
      "description": "nei giorni senza notizie, una storia vera dall'archivio",
      "type": "boolean"
    },
    "smalltalking_enabled": {
      "description": "ogni giorno, in coda al briefing, due o tre storie brevi da raccontare",
      "type": "boolean"
    },
    "serper_enrich": {
      "description": "arricchire il briefing con ricerche web fresche",
      "type": "boolean"
    }
  },
  "description": "Any subset of the settings.",
  "additionalProperties": false
}

tune_topic

Tune 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.

Parameters3

topic	string	optional	One key: a topic as it appears in get_information_diet or in a briefing entry (e.g. "intelligenza artificiale", "e:tesla", "c:auto")
topics	array	optional	Alternative to topic: labels to COMBINE with AND (e.g. ["e:tesla","f:soldi"])
action	string	required	What to change about it

Raw schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "One key: a topic as it appears in get_information_diet or in a briefing entry (e.g. \"intelligenza artificiale\", \"e:tesla\", \"c:auto\")"
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 4,
      "description": "Alternative to topic: labels to COMBINE with AND (e.g. [\"e:tesla\",\"f:soldi\"])"
    },
    "action": {
      "type": "string",
      "enum": [
        "more",
        "less",
        "more_technical",
        "simpler",
        "deeper",
        "shorter",
        "more_often",
        "less_often",
        "mute",
        "unmute",
        "follow",
        "unfollow"
      ],
      "description": "What to change about it"
    }
  },
  "required": [
    "action"
  ],
  "additionalProperties": false
}

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". 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.

Parameters3

note	string	required	What was wrong or what they want changed, in their own words
briefing_id	string	optional	Which briefing the note refers to. Omit for the latest.
entry_id	string	optional	Optional: the specific story the note is about (entry id from get_briefing)

Raw schema

{
  "type": "object",
  "properties": {
    "note": {
      "type": "string",
      "description": "What was wrong or what they want changed, in their own words"
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing the note refers to. Omit for the latest."
    },
    "entry_id": {
      "type": "string",
      "description": "Optional: the specific story the note is about (entry id from get_briefing)"
    }
  },
  "required": [
    "note"
  ],
  "additionalProperties": false
}

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. 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.

Parameters5

entry_id	string	required	Entry id from get_briefing
signal	string	required	The signal to record
topics	array	optional	Labels of this story to combine (AND), from `labels` in get_briefing — e.g. ["e:tesla"] for Tesla everywhere, ["e:tesla","f:soldi"] for Tesla only about money. Omit for the whole story.
briefing_id	string	optional	Which briefing. Omit for the latest.
withdraw	boolean	optional	true = take back the signal of this kind previously given on this story (the topics it had touched are restored). With "follow" use "unfollow" instead.

Raw schema

{
  "type": "object",
  "properties": {
    "entry_id": {
      "type": "string",
      "description": "Entry id from get_briefing"
    },
    "signal": {
      "type": "string",
      "enum": [
        "more",
        "less",
        "more_technical",
        "simpler",
        "deeper",
        "shorter",
        "more_often",
        "less_often",
        "mute",
        "follow",
        "unfollow"
      ],
      "description": "The signal to record"
    },
    "topics": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 6,
      "description": "Labels of this story to combine (AND), from `labels` in get_briefing — e.g. [\"e:tesla\"] for Tesla everywhere, [\"e:tesla\",\"f:soldi\"] for Tesla only about money. Omit for the whole story."
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    },
    "withdraw": {
      "type": "boolean",
      "description": "true = take back the signal of this kind previously given on this story (the topics it had touched are restored). With \"follow\" use \"unfollow\" instead."
    }
  },
  "required": [
    "entry_id",
    "signal"
  ],
  "additionalProperties": false
}

unfollow_story

Release 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.

Parameters1

story_id

string

required

The story id listed by get_information_diet

Raw schema

{
  "type": "object",
  "properties": {
    "story_id": {
      "type": "string",
      "description": "The story id listed by get_information_diet"
    }
  },
  "required": [
    "story_id"
  ],
  "additionalProperties": false
}

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 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.

Parameters2

text	string	required	What story they expected, in their own words
briefing_id	string	optional	Which briefing it was missing from. Omit for the latest.

Raw schema

{
  "type": "object",
  "properties": {
    "text": {
      "type": "string",
      "description": "What story they expected, in their own words"
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing it was missing from. Omit for the latest."
    }
  },
  "required": [
    "text"
  ],
  "additionalProperties": false
}

list_missing_reports

The 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.

Parameters1

briefing_id

string

optional

Which briefing. Omit for the latest.

Raw schema

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}

add_proposed_source

When 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.

Parameters1

report_id

string

required

The investigation id, from list_missing_reports or the report_missing_story result

Raw schema

{
  "type": "object",
  "properties": {
    "report_id": {
      "type": "string",
      "description": "The investigation id, from list_missing_reports or the report_missing_story result"
    }
  },
  "required": [
    "report_id"
  ],
  "additionalProperties": false
}

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 than replacing: pass mode "append" to add a line.

Parameters2

text	string	required	The profile text, or the line to add
mode	string	optional	Default append

Raw schema

{
  "type": "object",
  "properties": {
    "text": {
      "type": "string",
      "description": "The profile text, or the line to add"
    },
    "mode": {
      "type": "string",
      "enum": [
        "append",
        "replace"
      ],
      "description": "Default append"
    }
  },
  "required": [
    "text"
  ],
  "additionalProperties": false
}

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 about X" or "keep digging on this".

Parameters1

query

string

required

The question or topic to research

Raw schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "The question or topic to research"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

cancel_deep_dive

Remove a deep-dive request that is still waiting (ids from list_deep_dives). One already covered in a briefing cannot be cancelled.

Parameters1

deep_dive_id

string

required

The request id, from list_deep_dives

Raw schema

{
  "type": "object",
  "properties": {
    "deep_dive_id": {
      "type": "string",
      "description": "The request id, from list_deep_dives"
    }
  },
  "required": [
    "deep_dive_id"
  ],
  "additionalProperties": false
}

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 summarised even if the site later blocks access.

Parameters3

url	string	optional	The link to save
text	string	optional	Alternative to url: a free-text note to keep
title	string	optional	Optional title for a text note

Raw schema

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "The link to save"
    },
    "text": {
      "type": "string",
      "description": "Alternative to url: a free-text note to keep"
    },
    "title": {
      "type": "string",
      "description": "Optional title for a text note"
    }
  },
  "additionalProperties": false
}

save_entry

Keep 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.

Parameters2

entry_id	string	required	Entry id from get_briefing, or "chicca"
briefing_id	string	optional	Which briefing. Omit for the latest.

Raw schema

{
  "type": "object",
  "properties": {
    "entry_id": {
      "type": "string",
      "description": "Entry id from get_briefing, or \"chicca\""
    },
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "required": [
    "entry_id"
  ],
  "additionalProperties": false
}

unsave_entry

Take a story out of the reading list, by its saved id (from list_saved) or by briefing + entry id.

Parameters3

saved_id	string	optional	The id from list_saved
entry_id	string	optional	Alternative: the entry id in its briefing
briefing_id	string	optional	With entry_id: which briefing. Omit for the latest.

Raw schema

{
  "type": "object",
  "properties": {
    "saved_id": {
      "type": "string",
      "description": "The id from list_saved"
    },
    "entry_id": {
      "type": "string",
      "description": "Alternative: the entry id in its briefing"
    },
    "briefing_id": {
      "type": "string",
      "description": "With entry_id: which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}

share_briefing

Create (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.

Parameters2

briefing_id	string	optional	Which briefing. Omit for the latest.
podcast	boolean	optional	Include the episode in the shared page (default: unchanged, initially false)

Raw schema

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    },
    "podcast": {
      "type": "boolean",
      "description": "Include the episode in the shared page (default: unchanged, initially false)"
    }
  },
  "additionalProperties": false
}

unshare_briefing

Revoke the public link of a briefing: the page and its audio stop answering immediately.

Parameters1

briefing_id

string

optional

Which briefing. Omit for the latest.

Raw schema

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}

generate_podcast_episode

Make (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.

Parameters1

briefing_id

string

optional

Which briefing. Omit for the latest.

Raw schema

{
  "type": "object",
  "properties": {
    "briefing_id": {
      "type": "string",
      "description": "Which briefing. Omit for the latest."
    }
  },
  "additionalProperties": false
}

resume_podcast

The 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.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

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 explicitly asked. Returns the id to poll with get_briefing.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

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 you add a whole new subject to someone's information diet.

Parameters2

name	string	required	Short name, e.g. "AI research" or "Local news"
description	string	optional	Optional brief: what the reader expects from this inbox and what to skip — the editor reads it at every briefing

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Short name, e.g. \"AI research\" or \"Local news\""
    },
    "description": {
      "type": "string",
      "description": "Optional brief: what the reader expects from this inbox and what to skip — the editor reads it at every briefing"
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}

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 or pause it entirely.

Parameters7

source_id	string	required	Id from list_sources
name	string	optional	New name for the inbox
description	string	optional	The inbox brief: what the reader expects from it and what to skip — the editor reads it at every briefing
priority	integer	optional	1 marginal … 5 always first
include_in_digest	boolean	optional	false = keep collecting but leave it out of the briefing
is_active	boolean	optional	false = stop collecting entirely
technicality	integer	optional	Override just for this inbox

Raw schema

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Id from list_sources"
    },
    "name": {
      "type": "string",
      "description": "New name for the inbox"
    },
    "description": {
      "type": "string",
      "description": "The inbox brief: what the reader expects from it and what to skip — the editor reads it at every briefing"
    },
    "priority": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "description": "1 marginal … 5 always first"
    },
    "include_in_digest": {
      "type": "boolean",
      "description": "false = keep collecting but leave it out of the briefing"
    },
    "is_active": {
      "type": "boolean",
      "description": "false = stop collecting entirely"
    },
    "technicality": {
      "type": "integer",
      "minimum": 1,
      "maximum": 5,
      "description": "Override just for this inbox"
    }
  },
  "required": [
    "source_id"
  ],
  "additionalProperties": false
}

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_active false when in doubt.

Parameters1

source_id

string

required

Id from list_sources

Raw schema

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Id from list_sources"
    }
  },
  "required": [
    "source_id"
  ],
  "additionalProperties": false
}

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 precise (blocked by the site, gone, unreadable) so it can be reported honestly.

Parameters2

source_id	string	required	Which inbox (from list_sources)
url	string	required	Feed URL or plain site address, e.g. "ilpost.it"

Raw schema

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Which inbox (from list_sources)"
    },
    "url": {
      "type": "string",
      "description": "Feed URL or plain site address, e.g. \"ilpost.it\""
    }
  },
  "required": [
    "source_id",
    "url"
  ],
  "additionalProperties": false
}

remove_feed

Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it.

Parameters1

feed_id

string

required

Id from get_source

Raw schema

{
  "type": "object",
  "properties": {
    "feed_id": {
      "type": "string",
      "description": "Id from get_source"
    }
  },
  "required": [
    "feed_id"
  ],
  "additionalProperties": false
}

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 "news" watches the news index, "search" the whole web.

Parameters3

source_id	string	required	Which inbox (from list_sources)
query	string	required	The query, as you would type it into Google
kind	string	optional	Default news

Raw schema

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Which inbox (from list_sources)"
    },
    "query": {
      "type": "string",
      "description": "The query, as you would type it into Google"
    },
    "kind": {
      "type": "string",
      "enum": [
        "news",
        "search"
      ],
      "description": "Default news"
    }
  },
  "required": [
    "source_id",
    "query"
  ],
  "additionalProperties": false
}

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.

Parameters1

search_id

string

required

Id from get_source

Raw schema

{
  "type": "object",
  "properties": {
    "search_id": {
      "type": "string",
      "description": "Id from get_source"
    }
  },
  "required": [
    "search_id"
  ],
  "additionalProperties": false
}

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 monitoring, and newsletters worth subscribing to. Nothing is added — it returns proposals to pass to add_feed / add_web_search.

Parameters2

source_id	string	required	The inbox the proposals are for (its existing sources are excluded)
description	string	required	What they want to follow, in plain words

Raw schema

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "The inbox the proposals are for (its existing sources are excluded)"
    },
    "description": {
      "type": "string",
      "description": "What they want to follow, in plain words"
    }
  },
  "required": [
    "source_id",
    "description"
  ],
  "additionalProperties": false
}

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 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).

Parameters4

source_id	string	required	Which inbox to import into
opml	string	required	The full OPML/XML file contents
dry_run	boolean	optional	true = only list what would be imported
limit	integer	optional	Max feeds to add in this call (default 20 — big imports go in batches)

Raw schema

{
  "type": "object",
  "properties": {
    "source_id": {
      "type": "string",
      "description": "Which inbox to import into"
    },
    "opml": {
      "type": "string",
      "description": "The full OPML/XML file contents"
    },
    "dry_run": {
      "type": "boolean",
      "description": "true = only list what would be imported"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 40,
      "description": "Max feeds to add in this call (default 20 — big imports go in batches)"
    }
  },
  "required": [
    "source_id",
    "opml"
  ],
  "additionalProperties": false
}

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 to open, and says so honestly.

Parameters1

newsletter_id

string

required

Id from get_source (newsletters)

Raw schema

{
  "type": "object",
  "properties": {
    "newsletter_id": {
      "type": "string",
      "description": "Id from get_source (newsletters)"
    }
  },
  "required": [
    "newsletter_id"
  ],
  "additionalProperties": false
}

README.md10 KBView on GitHub

Proofite MCP server

Give your AI assistant the keys to your information diet.

Proofite turns the sources you choose — newsletters, RSS feeds, monitored web searches, saved links — into one personal briefing every morning, written by AI and available as a podcast. This MCP server lets any agent read that briefing and, more importantly, retune the filter behind it: what gets in, how deep, how technical, how often, and what never appears again.

It is the same server the product uses for its own voice mode, so it is not a demo surface: it is how Proofite is driven.

code

you   → "too much crypto this week, and go deeper on the EU regulation"
agent → correct_briefing(note: "…")
        → topic weights adjusted, depth raised, deep dive queued
        → tomorrow's briefing is different

Install

Remote (recommended). Streamable HTTP, no install. Create a key in Proofite under Settings → Connections, then:

bash

claude mcp add --transport http proofite https://proofite.com/mcp \
  --header "Authorization: Bearer pfk_live_…"

Or in any client that reads a JSON config:

json

{
  "mcpServers": {
    "proofite": {
      "type": "http",
      "url": "https://proofite.com/mcp",
      "headers": { "Authorization": "Bearer pfk_live_…" }
    }
  }
}

stdio bridge, for clients that do not speak HTTP yet:

json

{
  "mcpServers": {
    "proofite": {
      "command": "npx",
      "args": ["-y", "proofite-mcp"],
      "env": { "PROOFITE_API_KEY": "pfk_live_…" }
    }
  }
}

Tools

Tool		What it does
`get_briefing`	read	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 default, or a specific one by id or date. Also returns an index of entry ids, needed to rate or correct individual stories.
`list_briefings`	read	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.
`get_information_diet`	read	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, and the per-topic preferences built from their feedback (affinity, muted, followed). This is the full picture of their news filter — read it before changing anything.
`list_sources`	read	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 priority and whether it is included in the briefing.
`get_source`	read	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 or reorganising anything.
`get_podcast_episode`	read	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.
`list_read_later`	read	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	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	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.
`update_information_diet`	write	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 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).
`tune_topic`	write	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 gets reported. This is the precise instrument — for a vague comment like "too much crypto lately" use correct_briefing instead.
`correct_briefing`	write	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 the note against the actual briefing and turns it into concrete adjustments: topic preferences, settings, deep-dive requests. This is the main way a person retunes their news feed by talking.
`rate_briefing_entry`	write	Give a precise up/down signal on one story of a briefing: more like this, less like this, more technical, simpler, deeper, shorter, follow it, or mute its topics. Applies to the topics of that story, so the next briefing weighs them differently.
`set_learned_profile`	write	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 add a line.
`request_deep_dive`	write	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".
`save_for_later`	write	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 access.
`generate_briefing`	write	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 poll with get_briefing.
`create_source`	write	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 information diet.
`update_source`	write	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.
`delete_source`	write	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.
`add_feed`	write	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, unreadable) so it can be reported honestly.
`remove_feed`	write	Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it.
`add_web_search`	write	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, "search" the whole web.
`remove_web_search`	write	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	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 subscribing to. Nothing is added — it returns proposals to pass to add_feed / add_web_search.
`import_opml`	write	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 add them (they are validated one by one, and the ones that fail come back with the reason).
`unsubscribe_newsletter`	write	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.

It also exposes resources (proofite://briefing/latest, proofite://diet, proofite://sources) and two prompts (tune-my-feed, catch-me-up).

Notes that matter

Keys can be read-only, and the server enforces it: a read-only key cannot change a setting however convincingly it is asked. Create one per client, revoke individually.
Changes apply from the next briefing, never retroactively.
Scoped to one account. The key identifies a person; the server has no way to reach anyone else's information.
Protocol. Streamable HTTP. Speaks the 2026-07-28 revision (stateless, per-request _meta, mirrored Mcp-Method / Mcp-Name headers, server/discover) and the older initialize handshake used by most clients today — it detects which era you speak from your first request.

Requirements

A Proofite account — free trial, no card. The briefing, the podcast and this server are the same product seen from three sides.

Install

Tools (40)

get_briefinglist_briefingsget_information_dietlist_sourcesget_sourceget_podcast_episodeget_episode_transcriptlist_read_later

Configuration

Environment variables

PROOFITE_API_KEYrequiredsecret

Your Proofite API key, created at https://proofite.com/app/settings → Connections

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "proofite": {
      "command": "npx",
      "args": [
        "-y",
        "proofite-mcp@1.2.0"
      ],
      "env": {
        "PROOFITE_API_KEY": "<YOUR_PROOFITE_API_KEY>"
      }
    }
  }
}

Proofite MCP Server (com.proofite/proofite)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

get_briefing

list_briefings

get_information_diet

list_sources

get_source

get_podcast_episode

get_episode_transcript

list_read_later

list_deep_dives

list_saved

get_account

update_information_diet

tune_topic

correct_briefing

rate_briefing_entry

unfollow_story

report_missing_story

list_missing_reports

add_proposed_source

set_learned_profile

request_deep_dive

cancel_deep_dive

save_for_later

save_entry

unsave_entry

share_briefing

unshare_briefing

generate_podcast_episode

resume_podcast

generate_briefing

create_source

update_source

delete_source

add_feed

remove_feed

add_web_search

remove_web_search

discover_sources

import_opml

unsubscribe_newsletter

Proofite MCP server

Install

Tools

Notes that matter

Requirements

Links

Install

Configuration

Related servers