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