Sato Hub
MCP

eth-mcp

MCP server enabling agents to build and deploy Ethereum apps with Scaffold-ETH — clone, fork, deploy, and run local Web3 dev flows.

  • Sato Score55
  • ChainsEthereum
EarlyUnverifiedQuiet · 9mo ago

eth-mcp is an open-source MCP server on Ethereum, with last code activity on 2026-01-12 (Quiet). Latest release on 2026-01-09. Sato Score 55/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install eth-mcp →

Last commit Jan 12, 2026 · Last release Jan 9, 2026 · ★ 2

Listed from github.com/austintgriffith/eth-mcp on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-14. Evidence →

Website ↗GitHub ↗

Next step

Watch eth-mcp

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on austintgriffith/eth-mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Built by Austin Griffith (BuidlGuidl/Scaffold-ETH), eth-mcp gives an agent tools to clone Scaffold-ETH projects, manage long-running dev processes (Anvil forks, contract deployment, frontends), and pull DeFi address/yield reference data, published as the npm package eth-mcp. Development was concentrated in a short burst (January 2026) with 26 commits and 4 releases; the project notes it's local-development-only with basic error recovery, so treat it as an early, credible-maintainer tool rather than a polished product.

Sato Score

55/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
17/20
Interface verifiability
8/10
Docs & demo
0/10
Listing transparency & provenance
8/15
Independent verification
2/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

View verification & embed badge →History →How the Sato Score works

Sato Check

v0.7.0 · as of 2026-09-29
Does it take your key?
No key read found
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from github.com/austintgriffith/eth-mcp on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-14.

ClaimValueEvidenceSourceChecked
Chains supportedEthereumself-reportedgithub.com/austintgriffith/eth-mcpas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedgithub.com/austintgriffith/eth-mcpas of 2026-10-21
Recent activitylast release 2026-01-09 · last commit 2026-01-12observedgithub.com/austintgriffith/eth-mcp2026-10-21
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/austintgriffith/eth-mcp2026-09-14
Website answersanswered (HTTP 200)observedgithub.com/austintgriffith/eth-mcp2026-10-21
Daily check record88 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-09-29
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-29
Works withCursor, Scaffold-ETH, Foundry, Next.js, Anvil, mcp-server-ens, Blockscout MCP s…confidence 0.80self-reportedgithub.com/austintgriffith/eth-mcpas of 2026-08-07
Sato Score55/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Sep 14, 2026

Runtime: Node.js (npx package or build from source); expects Foundry tools (forge, anvil, cast) on PATH

npx -y eth-mcp@latest
{"mcpServers":{"eth-mcp":{"command":"npx","args":["-y","eth-mcp@latest"]}}}

You supply: No env vars documented; docs note the server blocks access to .env files and sanitizes output to remove private keys, Local toolchain: git, npm/yarn/pnpm, Foundry (forge, anvil, cast)

MCP invocation: npx -y eth-mcp@latest (stdio); local build: git clone + npm install + npm run build, then node dist/index.js

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

97.8%of 91 checks since 2026-07-23 succeeded
Currently responding for 33 days
Succeeded
89
Failed
2
Their error
0
Unattributed
2

State changed on 2026-09-07 (responding → unreachable from our probe), 2026-09-08 (unreachable from our probe → responding), 2026-09-18 (responding → unreachable from our probe), 2026-09-19 (unreachable from our probe → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
55
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Ethereum
Agent types
MCP server / dev-environment tool
Open source
Yes
Works with
Cursor, Scaffold-ETH, Foundry, Next.js, Anvil, mcp-server-ens, Blockscout MCP server, DefiLlama
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#scaffold-eth#developer-tool#local-dev
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to eth-mcp's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 19, 2026
    Sato Score tier: Low → Medium
    Score 39 → 54.
  2. Sep 18, 2026
    Sato Score tier: Medium → Low
    Score 54 → 39.
  3. Sep 14, 2026
    Verified: deploy spec
  4. Sep 8, 2026
    Sato Score tier: Low → Medium
    Score 32 → 46.
  5. Sep 7, 2026
    Sato Score tier: Medium → Low
    Score 47 → 32.
  6. Aug 7, 2026
    Auto-enriched: supported integrations
  7. Jul 24, 2026
    Sato Hub began tracking this listing
  8. Jul 19, 2026
    Listed on Sato Hub

Compared with

Alternatives to eth-mcp →

Appears in

Related Resources

Coinbase AgentKit

Active
Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain
Active★ 1.3k

Hyperliquid

Active
VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid
Recent★ 506▸ Jun 2023

Model Context Protocol (MCP)

Active
Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown
Active★ 9.5k

Reference

QuestionsShowHide

Questions people ask about eth-mcp

Is eth-mcp open source?
Yes. eth-mcp is open source under the MIT license; the repository is https://github.com/austintgriffith/eth-mcp. Checked as of 2026-10-21.
Which chains does eth-mcp support?
eth-mcp lists support for Ethereum as of 2026-10-21.
Is eth-mcp still maintained?
The most recent code activity Sato Hub observed was on 2026-01-12 (last commit 2026-01-12, last release 2026-01-09), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run eth-mcp?
Node.js (npx package or build from source); expects Foundry tools (forge, anvil, cast) on PATH. Install: npx -y eth-mcp@latest. Entry: {"mcpServers":{"eth-mcp":{"command":"npx","args":["-y","eth-mcp@latest"]}}}. Sato Hub reproduced this install in a container on 2026-09-14. It runs as an MCP server (npx -y eth-mcp@latest (stdio); local build: git clone + npm install + npm run build, then node dist/index.js).
Is eth-mcp verified on Sato Hub?
Sato Hub holds one earned check for eth-mcp: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 55 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "eth-mcp — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/eth-mcp-austingriffith

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.