get_information_diet — proofite MCP Tool Read-only
get_information_diet
(get information diet) is one of 28 tools on the
proofite
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_information_diet from your client
- Claude Code proofite get_information_diet run in your project directory
- Claude Desktop proofite get_information_diet ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor proofite get_information_diet ~/.cursor/mcp.json
- VS Code proofite get_information_diet .vscode/mcp.json
- Zed proofite get_information_diet ~/.config/zed/settings.json
- Windsurf proofite get_information_diet ~/.codeium/windsurf/mcp_config.json
- Cline proofite get_information_diet ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI proofite get_information_diet ~/.gemini/settings.json
- Grok proofite get_information_diet .mcp.json (in your project root)
- ChatGPT proofite get_information_diet Settings → Connectors → Advanced → Developer mode
- Claude.ai proofite get_information_diet Settings → Connectors → Add custom connector
- LangChain proofite get_information_diet pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http proofite https://proofite.com/mcpOther tools on this server
- get_briefing
- list_briefings
- list_sources
- get_source
- get_podcast_episode
- list_read_later
- list_deep_dives
- get_account
- update_information_diet
- tune_topic
- correct_briefing
- rate_briefing_entry
- report_missing_story
- set_learned_profile
- request_deep_dive
- save_for_later
- generate_briefing
- create_source
- update_source
- delete_source
- add_feed
- remove_feed
- add_web_search
- remove_web_search
- discover_sources
- import_opml
- unsubscribe_newsletter
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.