# Proofite MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.proofite%2Fproofite
Registry id: `mcp-registry/com.proofite/proofite`
Status: live (checked 2026-10-27T02:17:28.067Z)

## Verdict

Proofite MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 1056 ms median handshake and 6 outages in 90 days. Its agent-readiness grade is A (95/100) across 40 tools, costing an agent about 7,153 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 1056 ms | 18% of MCP servers |
| p95 handshake latency | 3621 ms | — |
| Checks in 30 days | 4,940 | — |
| Outages, 90 days | 6 | — |
| Median recovery | 5 min | — |
| Agent-readiness score | 95/100 (A) | 80% of MCP servers |
| Tools | 40 | — |
| Tool-list size for an agent | ~7,153 tokens | 34% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "proofite-mcp-server": {
      "type": "http",
      "url": "https://proofite.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http proofite-mcp-server https://proofite.com/mcp
```

## Tools (40)

- `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, 
- `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 — t
- `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 h
- `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.
- `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 p
- `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 sear
- `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_
- `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),
- `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,
- `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.
- `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 accru
- `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 we
- `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 pla
- `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 
- `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 sin
- `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 currentl
- `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
- `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 
- `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_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 pers
- `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 pe
- `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 
- `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 
- `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 typ
- `remove_feed`: Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it.
- `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.
- `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 br
- `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 
- `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 th
- `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 — th
- `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, 
- `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. Appendin
- `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 al
- `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 le
- `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 briefin
- `unsave_entry`: Take a story out of the reading list, by its saved id (from list_saved) or by briefing + entry id.
- `unshare_briefing`: Revoke the public link of a briefing: the page and its audio stop answering immediately.
- `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 t
- `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 sho
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.