OpenZeppelin MCP
Official OpenZeppelin MCP for generating template-based smart contracts in Solidity, Cairo, Stylus, and Stellar.
- Sato Score38
- ChainsEthereum, Arbitrum +1
OpenZeppelin MCP is a MCP server by OpenZeppelin on Ethereum and Arbitrum, with no code activity tracked. Sato Score 38/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install OpenZeppelin MCP →No code activity tracked
Listed from mcp.openzeppelin.com on 2026-07-12. Install: reproduced by Sato Hub on 2026-09-21. Evidence →
Next step
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpAsk Sato Hub what is on record about OpenZeppelin MCP 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
OpenZeppelin's hosted MCP server generates smart contracts from OpenZeppelin's established contract templates across Solidity (Ethereum), Cairo (Starknet), Arbitrum Stylus, Stellar, confidential contracts, and Uniswap Hooks. Run by OpenZeppelin, it lets an AI coding agent scaffold production-pattern contracts instead of writing them from scratch. A builder wires it into a developer agent's contract-generation step at mcp.openzeppelin.com.
Sato Score
38/100· LowHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 0/20
- Interface verifiability
- 8/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 3/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v0.7.1 · as of 2026-09-27- Does it take your key?
- No key read found
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
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 mcp.openzeppelin.com on 2026-07-12. Install: reproduced by Sato Hub on 2026-09-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Ethereum, Arbitrum, Multichain | self-reported | mcp.openzeppelin.com | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | mcp.openzeppelin.com | as of 2026-10-15 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | raw.githubusercontent.com | 2026-09-21 |
| Website answers | answered (HTTP 200) | observed | mcp.openzeppelin.com | 2026-10-15 |
| Daily check record | 90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-09-27 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-27 |
| Tags | smart-contracts, code-generation, solidity, cairo, stylus, stellar, uniswap-hoo…confidence 0.70 | self-reported | mcp.openzeppelin.com | as of 2026-07-14 |
| Sato Score | 38/100 (Low)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
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 21, 2026
Runtime: Node.js (npm package, runs via npx)
npx -y @openzeppelin/contracts-mcp
claude mcp add OpenZeppelinContracts -- npx -y @openzeppelin/contracts-mcp
{"command": "npx", "args": ["-y", "@openzeppelin/contracts-mcp"]}claude mcp add satohub-openzeppelin-mcp -- npx -y @openzeppelin/contracts-mcp
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-09-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- 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. 46 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-15, 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, Arbitrum, Multichain
- Agent types
- MCP Server, Developer Agent
- Open source
- Unknown
- Last checked
- 2026-10-15
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 OpenZeppelin MCP fits
Related concepts: What Are Onchain Agents?, How Agents Use Wallets
Listing History
Recorded changes to OpenZeppelin MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 21, 2026Verified: deploy spec
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Enriched: tags
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
ERC-8004: Trustless Agents
ActiveEthereum standard providing on-chain identity, reputation, and validation registries for AI agents.
Phantom MCP
ActivePhantom's MCP server that lets AI agents view addresses, sign transactions, swap, and transfer tokens across Solana, Ethereum, Bitcoin, and Sui.
Bankless Onchain MCP
UnknownMCP server providing AI assistants read access to onchain data via the Bankless API.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about OpenZeppelin MCP
- Is OpenZeppelin MCP open source?
- Unknown. Sato Hub has not found a public repository or a license statement for OpenZeppelin MCP as of 2026-10-15.
- Which chains does OpenZeppelin MCP support?
- OpenZeppelin MCP lists support for Ethereum, Arbitrum, Multichain as of 2026-10-15.
- Is OpenZeppelin MCP still maintained?
- Sato Hub tracks no commit or release for OpenZeppelin MCP; it cannot say whether it is maintained.
- How do I install or run OpenZeppelin MCP?
- Node.js (npm package, runs via npx). Install: npx -y @openzeppelin/contracts-mcp && claude mcp add OpenZeppelinContracts -- npx -y @openzeppelin/contracts-mcp. Entry: {"command": "npx", "args": ["-y", "@openzeppelin/contracts-mcp"]}. Sato Hub reproduced this install in a container on 2026-09-21. It runs as an MCP server (npx -y @openzeppelin/contracts-mcp (stdio)).
- Is OpenZeppelin MCP verified on Sato Hub?
- Sato Hub holds one earned check for OpenZeppelin MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 38 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "OpenZeppelin MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/openzeppelin-mcpData last refreshed 2026-10-15; 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.