Blockchain Mcp Powered By Tatum

Created By
tatumioa year ago
A Model Context Protocol (MCP) server providing access to Tatum's blockchain API across 130+ networks with tools including RPC Gateway and Blockchain Data insights. 130+ Blockchain Networks: Bitcoin, Ethereum, Polygon, Arbitrum, Base, Avalanche, and many more 🔗 Blockchain Data: Blocks, transactions, balances, network info 🌐 RPC Gateway: Direct access to blockchain RPC endpoints
Overview

What is Blockchain MCP Powered By Tatum?

Blockchain MCP Powered By Tatum is a Model Context Protocol (MCP) server that provides access to Tatum's blockchain API across 130+ networks, offering tools such as RPC Gateway and Blockchain Data insights.

How to use Blockchain MCP?

To use Blockchain MCP, install it via npm and obtain your API key from the Tatum Dashboard. Integrate the server into your MCP client configuration to start making API calls.

Key features of Blockchain MCP?

  • Access to 130+ blockchain networks including Bitcoin, Ethereum, and more.
  • Tools for retrieving blockchain data such as blocks, transactions, and balances.
  • RPC Gateway for direct access to blockchain RPC endpoints.

Use cases of Blockchain MCP?

  1. Fetching blockchain data for analytics and reporting.
  2. Executing RPC calls for various blockchain operations.
  3. Integrating blockchain functionalities into applications seamlessly.

FAQ from Blockchain MCP?

  • What networks does Blockchain MCP support?

It supports over 130 networks including Bitcoin, Ethereum, and many others.

  • Is there a cost to use Blockchain MCP?

The service is free to use, but you need to obtain an API key from Tatum.

  • How can I get help with using Blockchain MCP?

You can refer to the Tatum API Documentation for detailed guidance.

Server Config

{
  "mcpServers": {
    "tatumio": {
      "command": "npx",
      "args": [
        "@tatumio/blockchain-mcp"
      ],
      "env": {
        "TATUM_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
Project Info
Hosted
Created At
a year ago
Updated At
a year ago
Author Name
tatumio
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

5 hours ago
Alloy

2 days ago