token.verdict — xytara MCP Executor MCP Tool
token.verdict
(token verdict) is one of 31 tools on the
xytara MCP Executor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call token.verdict from your client
- Claude Code xytara MCP Executor token.verdict run in your project directory
- Claude Desktop xytara MCP Executor token.verdict ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor xytara MCP Executor token.verdict ~/.cursor/mcp.json
- VS Code xytara MCP Executor token.verdict .vscode/mcp.json
- Zed xytara MCP Executor token.verdict ~/.config/zed/settings.json
- Windsurf xytara MCP Executor token.verdict ~/.codeium/windsurf/mcp_config.json
- Cline xytara MCP Executor token.verdict ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI xytara MCP Executor token.verdict ~/.gemini/settings.json
- Grok xytara MCP Executor token.verdict .mcp.json (in your project root)
- ChatGPT xytara MCP Executor token.verdict Settings → Connectors → Advanced → Developer mode
- Claude.ai xytara MCP Executor token.verdict Settings → Connectors → Add custom connector
- LangChain xytara MCP Executor token.verdict pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http xytara-mcp-executor https://mcp.naxytra.com/mcp
Other tools on this server
- summarize
- zones.lookup
- catalog
- reply.draft
- json.validate
- text.extract
- html.to-text
- text.chunk
- x402.decode
- keccak256
- address.validate
- x402.verify-receipt
- tx.status
- abi.encode
- abi.decode
- merkle.verify
- eip712.hash
- ai.chat
- ai.url-research
- ai.news-brief
- token.honeypot
- crypto.price
- crypto.feargreed
- crypto.news
- crypto.market-pulse
- web.read
- bounty.radar
- wallet.profile
- gas.base
- ai.research-pro
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.