Proofite is an MCP server with 27 tools an agent can call, among them add_feed, add_web_search, correct_briefing. It answers at https://proofite.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Read your AI-written daily briefing and retune the filter behind it: feeds, newsletters, topics.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 repor Inputs: source_id, url |
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. Inputs: source_id, query, kind |
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", "follow this story". An AI editor reads the note against the Inputs: note, briefing_id, entry_id |
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. Inputs: name, description |
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. Inputs: source_id |
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 Inputs: source_id, description |
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. |
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. |
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 Inputs: briefing_id, include_markdown |
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 learned about them, and the per-topic preferences built fro |
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 episode by default. Inputs: briefing_id |
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 anyt Inputs: source_id |
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 v Inputs: source_id, opml, dry_run, limit |
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. Inputs: limit |
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. |
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. |
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 |
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, follow it, or mute its topics. Applies to the topics of that story, so the next briefing weighs them differe Inputs: entry_id, signal, briefing_id |
remove_feed | Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it. Inputs: feed_id |
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. Inputs: search_id |
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". Inputs: query |
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. Inputs: url, text, title |
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. Inputs: text, mode |
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 development gets reported. This is the precise instrument — for Inputs: topic, action |
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. Inputs: newsletter_id |
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, podcast and email delivery. Pass only the keys you want to ch Inputs: digest_enabled, digest_time, digest_days, digest_length, technicality, depth |
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. Inputs: source_id, name, description, priority, include_in_digest, is_active |
Every block below points at https://proofite.com/mcp. Pick your client and copy.
claude mcp add --transport http proofite https://proofite.com/mcp
{
"mcpServers": {
"proofite": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://proofite.com/mcp"]
}
}
}{
"mcpServers": {
"proofite": {
"url": "https://proofite.com/mcp"
}
}
}{
"servers": {
"proofite": {
"type": "http",
"url": "https://proofite.com/mcp"
}
}
}{
"context_servers": {
"proofite": {
"url": "https://proofite.com/mcp"
}
}
}{
"mcpServers": {
"proofite": {
"serverUrl": "https://proofite.com/mcp"
}
}
}{
"mcpServers": {
"proofite": {
"url": "https://proofite.com/mcp"
}
}
}name: Proofite
version: 0.0.1
schema: v1
mcpServers:
- name: Proofite
type: streamable-http
url: https://proofite.com/mcp{
"mcpServers": {
"proofite": {
"httpUrl": "https://proofite.com/mcp"
}
}
}{
"mcpServers": {
"proofite": {
"type": "http",
"url": "https://proofite.com/mcp"
}
}
}{
"mcpServers": {
"proofite": {
"url": "https://proofite.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fproofite.com%2Fmcp&type=streamable_http&id=proofite&name=Proofite
It answered our last check on 18 October 2026 in 176 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by proofite.com and served from proofite.com, the vendor's own domain: https://proofite.com/mcp.
27, as returned by the server's own tools/list on 31 August 2026: add_feed, add_web_search, correct_briefing, create_source, delete_source, discover_sources, generate_briefing, get_account, and 19 more.
It answered our last check on 18 October 2026 in 176 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://proofite.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.proofite. Endpoint host: proofite.com. ARD identifier: urn:air:com.proofite:mcp:proofite.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.