# Proofite Muse connector From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta. ## Proofite Read and tune your AI-written daily news briefing by adjusting feeds, topics and preferences. - Record: https://musedirectory.ai/connector/proofite - Category: Productivity - Developer: Proofite (https://proofite.com/mcp) - Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse. - Health: Working, 227ms, checked 2026-09-28T07:46:08Z - Endpoint: https://proofite.com/mcp - Auth: Needs an access key; Pricing: unknown - Screening: Screened, no issues found (2026-09-24T18:11:00Z) - Source: Found in the official MCP Registry (com.proofite/proofite) https://registry.modelcontextprotocol.io/v0/servers?search=com.proofite%2Fproofite Connects to Proofite's personalized news briefing service. Muse can read your daily digest, adjust what topics and sources appear, rate individual stories, save links for later, and request deeper research on specific subjects. Example request: "Show me today's briefing and tell me I want less crypto news but more coverage of EU regulation." How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Proofite to help me. It is a free service with an MCP server at https://proofite.com/mcp. It needs an API key from Proofite; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer. Tools: - 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 - 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. - 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, the per-topic preferences built from their feedback (affinity, muted, followed - 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. - 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. - 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. - 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_deep_dives: List the deep-dive research requests waiting to be covered: topics the user asked the briefing to investigate with fresh web research. - 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. - 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 change. Read get_information_diet first — - 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 of that WHOLE THEME gets reported (to follow one specific story, use rate_briefing_entry wit - 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 actual briefing and turns it into concre - 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 its topics. These apply to the topics of that story, so the next briefing weighs them differently. A story usually has several topics: pass - 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 ca - 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. - 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". - 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. - 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. - 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. - 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. - 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. - 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. - remove_feed: Remove an RSS feed from a topic inbox. Already-collected content stays; nothing new arrives from it. - 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. - 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. - 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 - 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 f - 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. Screening checks: - MCP handshake: pass (Answered in 630ms) - Domain against threat feeds (Cloudflare security DNS): pass (proofite.com not flagged) - Published packages against the OSV malicious-package database: pass (No malicious-package advisories) - Hidden instructions or invisible characters in tool text: pass (28 tools read, nothing found) - Inputs asking for passwords, card numbers or seed phrases: pass (None found) - Domain and redirects: pass (No redirects off the domain) - AI review of purpose and tool behavior: pass (No concerns)