submit_deploy_claim — Countersign by Signalry MCP Tool
submit_deploy_claim
(submit deploy claim) 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 submit_deploy_claim from your client
- Claude Code Countersign by Signalry submit_deploy_claim run in your project directory
- Claude Desktop Countersign by Signalry submit_deploy_claim ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Countersign by Signalry submit_deploy_claim ~/.cursor/mcp.json
- VS Code Countersign by Signalry submit_deploy_claim .vscode/mcp.json
- Zed Countersign by Signalry submit_deploy_claim ~/.config/zed/settings.json
- Windsurf Countersign by Signalry submit_deploy_claim ~/.codeium/windsurf/mcp_config.json
- Cline Countersign by Signalry submit_deploy_claim ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Countersign by Signalry submit_deploy_claim ~/.gemini/settings.json
- Grok Countersign by Signalry submit_deploy_claim .mcp.json (in your project root)
- ChatGPT Countersign by Signalry submit_deploy_claim Settings → Connectors → Advanced → Developer mode
- Claude.ai Countersign by Signalry submit_deploy_claim Settings → Connectors → Add custom connector
- LangChain Countersign by Signalry submit_deploy_claim pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http countersign https://countersign.signalry.ai/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.