Chainlist MCP Server

Created By
kukapaya year ago
An MCP server that gives AI agents fast access to verified EVM chain information, including RPC URLs, chain IDs, explorers, and native tokens.
Overview

What is Chainlist MCP Server?

Chainlist MCP Server is an MCP server that provides AI agents with quick access to verified Ethereum Virtual Machine (EVM) chain information, including RPC URLs, chain IDs, explorers, and native tokens sourced from Chainlist.org.

How to use Chainlist MCP Server?

To use the Chainlist MCP Server, clone the repository from GitHub, install the necessary dependencies, and run the server using the MCP protocol with compatible clients.

Key features of Chainlist MCP Server?

  • Efficient data fetching with caching to minimize API requests.
  • Flexible search capabilities using regex for keyword matching.
  • Structured output in Markdown format for easy readability of RPC and explorer information.

Use cases of Chainlist MCP Server?

  1. Providing AI agents with real-time blockchain data.
  2. Assisting developers in accessing EVM chain information quickly.
  3. Enabling efficient blockchain data retrieval for applications and services.

FAQ from Chainlist MCP Server?

  • What is the purpose of Chainlist MCP Server?

It provides fast access to verified EVM chain information for AI agents and developers.

  • Is there a specific Python version required?

Yes, Python version 3.10 or higher is required.

  • How can I install the server?

You can install it by cloning the repository and following the installation steps provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kukapay
Star
0
Language
Python
License
MIT 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)

9 hours ago
Alloy

2 days ago