crypto_exchange_check — mcp MCP Tool
crypto_exchange_check
(crypto exchange check) is one of 34 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call crypto_exchange_check from your client
- Claude Code mcp crypto_exchange_check run in your project directory
- Claude Desktop mcp crypto_exchange_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp crypto_exchange_check ~/.cursor/mcp.json
- VS Code mcp crypto_exchange_check .vscode/mcp.json
- Zed mcp crypto_exchange_check ~/.config/zed/settings.json
- Windsurf mcp crypto_exchange_check ~/.codeium/windsurf/mcp_config.json
- Cline mcp crypto_exchange_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp crypto_exchange_check ~/.gemini/settings.json
- Grok mcp crypto_exchange_check .mcp.json (in your project root)
- ChatGPT mcp crypto_exchange_check Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp crypto_exchange_check Settings → Connectors → Add custom connector
- LangChain mcp crypto_exchange_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://dechonet.com/mcp
Other tools on this server
- dns_lookup
- ssl_check
- http_security
- email_auth
- port_scan
- dns_propagation
- reverse_dns
- asn_lookup
- whois_lookup
- subdomain_discovery
- lookalike_domains
- ip_info
- email_header_analysis
- subnet_calc
- security_scan
- owasp_check
- impersonation_exposure
- domain_changes
- domain_history
- infrastructure_pivot
- watch_domain
- set_expectations
- verify_expectations
- check_before_action
- crypto_check_before_sign
- wallet_address_check
- crypto_dapp_check
- report_page
- golive_check
- pqc_readiness
- mcp_server_check
- phishing_link_check
- exposure_map
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.