Base Network MCP Server

Created By
u-Operating-Systema year ago
MCP server for AI agents to query Base Network blockchain data.
Overview

what is Base Network MCP Server?

Base Network MCP Server is a Model Context Protocol (MCP) server designed for accessing and querying data from the Base Network blockchain, including blocks, transactions, balances, and smart contracts.

how to use Base Network MCP Server?

To use the server, clone the repository from GitHub, install the necessary dependencies, and run the server using npm. Optionally, you can enhance features by adding a BaseScan API key.

key features of Base Network MCP Server?

  • Supports 9 blockchain tools, with 7 available without an API key.
  • Access to both Base mainnet and Sepolia testnet.
  • Real-time blockchain data access.
  • Docker support for easy deployment.
  • Multiple transport options including stdio and HTTP.

use cases of Base Network MCP Server?

  1. Querying the latest block information from the blockchain.
  2. Retrieving transaction details for specific transactions.
  3. Checking balances and gas prices on the Base Network.
  4. Monitoring network statistics and account transaction history.

FAQ from Base Network MCP Server?

  • What is the purpose of the MCP server?

The MCP server allows AI agents and developers to easily access and query blockchain data from the Base Network.

  • Do I need an API key to use all features?

No, most features are available without an API key, but some tools require it for enhanced functionality.

  • How can I run the server in Docker?

You can run the server in Docker by using the provided commands in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
u-Operating-System
Star
0
Language
TypeScript
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)

a day ago