Skip to content

Claude.ai mcp transactions_data__transactions_data_evm

How to: Claude.ai mcp transactions_data__transactions_data_evm

client:Claude.ai transport:streamable-http tool:transactions_data__transactions_data_evm

Add mcp to Claude.ai

  1. 01

    Open Settings → Connectors → Add custom connector and merge this in. Keep any servers already there.

https://ai.cryptoapis.io/mcp
  1. 02

    Save the file and restart Claude.ai.

  2. 03

    Ask for something transactions_data__transactions_data_evm does. Claude.ai lists the server's tools on connect and calls transactions_data__transactions_data_evm itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that mcp's identifier in your config matches the one above exactly.

Claude on the web takes a remote URL and completes OAuth in the browser. For a packaged server use Claude Desktop or Claude Code instead. Claude.ai docs

Set these first

mcp will not start until these are set, so transactions_data__transactions_data_evm never becomes available.

  • CRYPTOAPIS_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 21 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.