get_decay_index — Countersign by Signalry MCP Tool Read-only
get_decay_index
(get decay index) 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_decay_index from your client
- Claude Code Countersign by Signalry get_decay_index run in your project directory
- Claude Desktop Countersign by Signalry get_decay_index ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Countersign by Signalry get_decay_index ~/.cursor/mcp.json
- VS Code Countersign by Signalry get_decay_index .vscode/mcp.json
- Zed Countersign by Signalry get_decay_index ~/.config/zed/settings.json
- Windsurf Countersign by Signalry get_decay_index ~/.codeium/windsurf/mcp_config.json
- Cline Countersign by Signalry get_decay_index ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Countersign by Signalry get_decay_index ~/.gemini/settings.json
- Grok Countersign by Signalry get_decay_index .mcp.json (in your project root)
- ChatGPT Countersign by Signalry get_decay_index Settings → Connectors → Advanced → Developer mode
- Claude.ai Countersign by Signalry get_decay_index Settings → Connectors → Add custom connector
- LangChain Countersign by Signalry get_decay_index 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.