get_freshness_summary — DataPulse MCP Tool Read-only
get_freshness_summary
(get freshness summary) is one of 19 tools on the
DataPulse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_freshness_summary from your client
- Claude Code DataPulse get_freshness_summary run in your project directory
- Claude Desktop DataPulse get_freshness_summary ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DataPulse get_freshness_summary ~/.cursor/mcp.json
- VS Code DataPulse get_freshness_summary .vscode/mcp.json
- Zed DataPulse get_freshness_summary ~/.config/zed/settings.json
- Windsurf DataPulse get_freshness_summary ~/.codeium/windsurf/mcp_config.json
- Cline DataPulse get_freshness_summary ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DataPulse get_freshness_summary ~/.gemini/settings.json
- Grok DataPulse get_freshness_summary .mcp.json (in your project root)
- ChatGPT DataPulse get_freshness_summary Settings → Connectors → Advanced → Developer mode
- Claude.ai DataPulse get_freshness_summary Settings → Connectors → Add custom connector
- LangChain DataPulse get_freshness_summary pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http datapulse-my https://mcp.data-pulse.my/mcpOther tools on this server
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.