← Registry

Productivity

proofite.com

Proofite aggregates newsletters, feeds, and web searches into a personalized AI-written daily digest with a morning podcast, helping users stay informed efficiently.

1 endpoint28 known toolsFirst detected August 17, 2026Last detected September 17, 2026

ENDPOINT 1

https://proofite.com/mcp

No auth detected

MCP server metadata

Name
proofite
Version
1.0.0
Capabilities
toolsresourcesprompts
Server instructions

Proofite turns the sources a person chooses — newsletters, RSS feeds, monitored web searches, saved links — into one personal daily briefing, also available as a podcast. This server is the control room for that: read what reached them (get_briefing), read the filter that decides what reaches them (get_information_diet), and change it. Two habits make you good at this: 1. Read before writing. get_information_diet and list_sources cost nothing and stop you from duplicating a feed or muting a topic they actually love. 2. Prefer their words to your inference. When someone says something vague about the briefing ("too much crypto lately"), pass it verbatim to correct_briefing: an editor that already knows the briefing turns it into concrete adjustments. Use tune_topic only when the topic and the direction are explicit. Changes take effect from the next briefing, not retroactively — say so when you report back.

Known tools 28

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.

Inferred read-only
list_briefings

List the user's past daily briefings (most recent first) with date, title, number of stories and whether an episode exists.

Inferred read-only
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 from their feedback (affinity, muted, followed).

Inferred read-only
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.

Potential side effects
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.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
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.

Inferred read-only
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.

Potential side effects
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.

Inferred read-only
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".

Inferred read-only
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.

Inferred read-only
report_missing_story

The reader expected a story and the briefing did not have it.

Inferred read-only
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.

Inferred read-only
request_deep_dive

Ask the next briefing to investigate a topic properly, with fresh web research: it will include a mini-dossier with sources.

Inferred read-only
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.

Inferred read-only
generate_briefing

Generate a briefing immediately instead of waiting for the scheduled time, using everything collected so far.

Inferred read-only
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.

Potential side effects
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.

Inferred read-only
delete_source

Permanently delete a topic inbox with all its feeds, searches and collected content.

Potential side effects
add_feed

Add an RSS/Atom feed to a topic inbox.

Inferred read-only
remove_feed

Remove an RSS feed from a topic inbox.

Potential side effects
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.

Inferred read-only
remove_web_search

Stop monitoring a standing web search: no new results from that query will reach the briefing.

Inferred read-only
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.

Inferred read-only
import_opml

Import subscriptions from another RSS reader (Feedly, Inoreader, FreshRSS, NetNewsWire) by passing the OPML file contents.

Inferred read-only
unsubscribe_newsletter

Unsubscribe from a newsletter arriving in one of the inboxes.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.proofite]
url = "https://proofite.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "proofite": {
      "type": "http",
      "url": "https://proofite.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: proofite
Remote MCP URL: https://proofite.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "proofite": {
      "url": "https://proofite.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "proofite": {
      "type": "http",
      "url": "https://proofite.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "proofite",
  "transport": "streamable-http",
  "url": "https://proofite.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for proofite.com was fetched 2026-08-23T21:33:29.654Z and is being refreshed.

Trust status Trusted

proofite.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.