1scan - Blockchain Explorer API Gateway & MCP Server

Created By
huahuayua year ago
A unified API gateway for integrating multiple etherscan-like blockchain explorer APIs with Model Context Protocol (MCP) support for AI assistants.
Overview

What is 1scan?

1scan is a unified API gateway designed for integrating multiple blockchain explorer APIs, providing support for the Model Context Protocol (MCP) to facilitate AI assistants in querying blockchain data.

How to use 1scan?

To use 1scan, install it via Go or from source, create a configuration file with your API keys, and run both the API server and MCP server. You can then integrate it with AI tools like Cursor IDE to access blockchain data.

Key features of 1scan?

  • Unified API endpoint for multiple blockchain explorers
  • API load balancing and rate limit management
  • Custom API key support via URL parameters
  • MCP server for AI assistants to query blockchain data

Use cases of 1scan?

  1. Accessing blockchain data for AI-driven applications
  2. Analyzing transactions and account balances across multiple blockchain networks
  3. Integrating blockchain data into AI conversations for enhanced user interaction

FAQ from 1scan?

  • Can I use 1scan with any blockchain explorer?

Yes, 1scan supports multiple blockchain explorers, and you can apply for API keys for each.

  • Is there a limit on API requests?

Yes, you can manage rate limits for each API key in your configuration file.

  • How do I integrate 1scan with AI tools?

You can integrate it with Cursor IDE by adding the MCP server URL in the settings.

Server Config

{
  "mcpServers": {
    "1scan": {
      "url": "http://localhost:3000/mcp/sse",
      "command": "1scanmcp"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
huahuayu
Star
2
Language
Go
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
Crevio

2 days ago