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