get_report — Every Signal MCP Tool Read-only
get_report
(get report) is one of 16 tools on the
Every Signal
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_report from your client
- Claude Code Every Signal get_report run in your project directory
- Claude Desktop Every Signal get_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Every Signal get_report ~/.cursor/mcp.json
- VS Code Every Signal get_report .vscode/mcp.json
- Zed Every Signal get_report ~/.config/zed/settings.json
- Windsurf Every Signal get_report ~/.codeium/windsurf/mcp_config.json
- Cline Every Signal get_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Every Signal get_report ~/.gemini/settings.json
- Grok Every Signal get_report .mcp.json (in your project root)
- ChatGPT Every Signal get_report Settings → Connectors → Advanced → Developer mode
- Claude.ai Every Signal get_report Settings → Connectors → Add custom connector
- LangChain Every Signal get_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http everysignal https://everysignal.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.