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