Ethereum History
BrowseFor Agents
Back to home

MCP Setup

Connect AI agents and MCP clients to Ethereum History

Ethereum History exposes a read-only, factual API for historical Ethereum mainnet contracts. Use the manifest URL below to register it as an MCP server or skill in Cursor, Claude, or other agents.

MCP Server URL

Ethereum History implements the Model Context Protocol (MCP) natively. Add this URL to Claude Desktop, Cursor, or any MCP-compatible client to give your AI agent direct access to Ethereum history tools.

https://www.ethereumhistory.com/mcp

Available Tools

  • ●get_contract — Full contract details (bytecode, decompiled code, history, links)
  • ●search_contracts — Search by name, token, code, address
  • ●browse_contracts — Browse with filters (era, type, year)
  • ●get_contract_of_the_day — Today's featured historical contract
  • ●get_documentation_progress — Stats and community metrics

Claude Desktop Config

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "ethereum-history": {
      "url": "https://www.ethereumhistory.com/mcp"
    }
  }
}

Manifest URL

Point your MCP client or agent at this URL. The manifest describes capabilities and endpoints (contract facts, discovery, temporal queries).

https://www.ethereumhistory.com/api/agent/manifest

Capabilities

  • contract_facts — Full data for one contract (bytecode, decompiled code, history, links, metadata) via GET /api/agent/contracts/{address}
  • discovery — List contracts with filters (era_id, featured, undocumented_only, limit, offset) via GET /api/agent/contracts
  • temporal_queries — Contracts by deployment time range (from_timestamp, to_timestamp, ISO 8601) on the same discovery endpoint

Cursor / Claude MCP

If your environment supports MCP (Model Context Protocol), add a server that fetches the manifest and exposes the Ethereum History endpoints. Configuration format depends on your client; typically you provide the manifest URL or a wrapper server URL.

Example: In Cursor MCP settings, you might add a custom server that uses https://www.ethereumhistory.com/api/agent/manifest as the source of truth for available tools (contract lookup, discovery, temporal queries).

Quick test

Fetch the manifest to verify connectivity:

curl "https://www.ethereumhistory.com/api/agent/manifest"

REST API (no MCP)

You can call the same endpoints directly over HTTP. No API key required. All methods are GET. See the full reference in the API docs.

  • • Contract by address: https://www.ethereumhistory.com/api/agent/contracts/0x...
  • • Discovery: https://www.ethereumhistory.com/api/agent/contracts?era_id=homestead&limit=10
  • • Temporal: https://www.ethereumhistory.com/api/agent/contracts?from_timestamp=2015-07-30T00:00:00Z&to_timestamp=2016-12-31T23:59:59Z

Terms

Read-only. No opinions or editorial stance. Data as documented on EthereumHistory.com. Ethereum History is a factual, non-opinionated historical data provider. Use the data for research, agents, and preservation; do not misuse or overload the public API.

API DocsBack to home