# hanicker/Proofite MCP Server

Source: https://glimind.com/server/glama%2Fhanicker%2Fproofite-mcp-server
Registry id: `glama/hanicker/proofite-mcp-server`
Status: unknown

## Tools (20)

- `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 history.
- `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,
- `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_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 pr
- `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.
- `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
- `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_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 
- `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 topic
- `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 
- `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
- `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 fo
- `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, l
- `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.