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