MetaMask mcp-x402
MetaMask's own MCP server for generating x402 payment headers signed by a supplied private key.
- Sato Score46
- ChainsEthereum, Base
MetaMask mcp-x402 is an open-source wallet infrastructure on Ethereum and Base, with last code activity on 2026-01-01 (Quiet). Sato Score 46/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 MetaMask mcp-x402 →Last commit Jan 1, 2026 · ★ 2
Listed from github.com/MetaMask/mcp-x402 on 2026-07-19. Install: failed on 2026-10-15. Evidence →
Next step
Watch MetaMask mcp-x402
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/mcpRun Sato Hub Preflight on metamask/mcp-x402 before I use it.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
mcp-x402 is a first-party MetaMask MCP server that constructs and signs x402 payment headers from a provided EVM private key, letting an agent complete x402-gated HTTP requests without hand-rolling payment-header logic. It targets agent builders who need machine-payable API access on EVM chains and want a MetaMask-maintained reference implementation rather than a third-party one.
Sato Score
46/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 17/20
- Interface verifiability
- 0/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 6/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from github.com/MetaMask/mcp-x402 on 2026-07-19. Install: failed on 2026-10-15.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Base | self-reported | github.com/MetaMask/mcp-x402 | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | github.com/MetaMask/mcp-x402 | as of 2026-10-21 |
| Recent activity | last commit 2026-01-01 | observed | github.com/MetaMask/mcp-x402 | 2026-10-21 |
| Install works | did not complete at the install stepa measurement of the documented path, often a stale README — not a judgement of the software | observed | github.com/MetaMask/mcp-x402 | 2026-10-15 |
| Website answers | answered (HTTP 200) | observed | github.com/MetaMask/mcp-x402 | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Sato Score | 46/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-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 — we ran this on Oct 15, 2026 and the install step did not complete — the commands below are the project's own, and they may simply have moved on
Runtime: Node.js (yarn build)
install: install failed: [4/4] Building fresh packages... | success Saved lockfile. | Done in 0.03s. | yarn run v1.22.22 | error Couldn't find a package.json file in "/app" | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ran: export COREPACK_ENABLE_DOWNLOAD_PROMPT=0; corepack enable || exit 1; mkdir -p /app || exit 1; cd /app || exit 1; yarn install && yarn build
entry: skipped (install failed)
ran: d="$(ls -d /app/*/ 2>/dev/null | head -1)"; { [ -n "$d" ] && cd "$d"; } || cd /app || exit 1; if timeout 8 node build/index.js </dev/null >/dev/null 2>&1; then c=0; else c=$?; fi; [ $c -eq 124 ] || [ $c -eq 0 ] || exit 3
yarn install yarn build node build/index.js
You supply: Private key for creating x402 payment headers (env var name not documented in README; .env.sample in repo) — signing-key risk
MCP invocation: node build/index.js (stdio); inspector: npx @modelcontextprotocol/inspector node build/index.js
Read from the project’s own docs as of 2026-10-15. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
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
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, Base
- Agent types
- MCP server / x402 tooling
- Open source
- Yes
- 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.
Where MetaMask mcp-x402 fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to MetaMask mcp-x402's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 15, 2026Verified: deploy spec
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Model Context Protocol (MCP)
ActiveAnthropic's open standard for connecting AI systems to external tools and data sources.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about MetaMask mcp-x402
- Is MetaMask mcp-x402 open source?
- Yes. MetaMask mcp-x402 is open source under the MIT license; the repository is https://github.com/MetaMask/mcp-x402. Checked as of 2026-10-21.
- Which chains does MetaMask mcp-x402 support?
- MetaMask mcp-x402 lists support for Ethereum, Base as of 2026-10-21.
- Is MetaMask mcp-x402 still maintained?
- The most recent code activity Sato Hub observed was on 2026-01-01 (last commit 2026-01-01), 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 MetaMask mcp-x402?
- Node.js (yarn build). Install: yarn install && yarn build. Entry: node build/index.js. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (node build/index.js (stdio); inspector: npx @modelcontextprotocol/inspector node build/index.js).
- Is MetaMask mcp-x402 verified on Sato Hub?
- No independent verification is on record for MetaMask mcp-x402; its verification status is "Unverified" and its Sato Score is 46 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "MetaMask mcp-x402 — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/metamask-mcp-x402Data 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.