token_check_demo — falcon.sol MCP Tool
token_check_demo
(token check demo) is one of 20 tools on the
falcon.sol
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call token_check_demo from your client
- Claude Code falcon.sol token_check_demo run in your project directory
- Claude Desktop falcon.sol token_check_demo ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor falcon.sol token_check_demo ~/.cursor/mcp.json
- VS Code falcon.sol token_check_demo .vscode/mcp.json
- Zed falcon.sol token_check_demo ~/.config/zed/settings.json
- Windsurf falcon.sol token_check_demo ~/.codeium/windsurf/mcp_config.json
- Cline falcon.sol token_check_demo ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI falcon.sol token_check_demo ~/.gemini/settings.json
- Grok falcon.sol token_check_demo .mcp.json (in your project root)
- ChatGPT falcon.sol token_check_demo Settings → Connectors → Advanced → Developer mode
- Claude.ai falcon.sol token_check_demo Settings → Connectors → Add custom connector
- LangChain falcon.sol token_check_demo pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http falcon-sol https://falcon-sol-agents.vercel.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 28 October 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.