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