OpenSea MCP
Official hosted OpenSea MCP: NFT, token, and wallet data plus swap quotes and mint actions for agents.
- Sato Score67
- ChainsMultichain
OpenSea MCP is a MCP server by OpenSea, with no code activity tracked. Sato Score 67/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 OpenSea MCP →No code activity tracked
Listed from opensea.io on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch OpenSea MCP
One email if what we observe changes — its endpoint stops answering, 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 https://mcp.opensea.io/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
OpenSea MCP is a hosted Streamable HTTP MCP server operated by OpenSea that exposes NFT collections and items, token/crypto data, wallet portfolio analysis, token swap quotes, NFT minting from drops, and trading activity. Builders plug it into an agent to query onchain marketplace and portfolio data or execute mint/swap flows without building custom OpenSea API integrations. Documented official support for Claude, ChatGPT, and Cursor.
Sato Score
67/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 0/20
- Interface verifiability
- 10/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 11/15
- Independent verification
- 5/10
Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).
Evidence — listed vs checked · what the words mean
Listed from opensea.io on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | docs.opensea.io | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | opensea.io | as of 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted by Sato Hub | self-reported | docs.opensea.io | as of 2026-07-14 |
| MCP endpoint answers | answered — 1 tools listed | observed | mcp.opensea.io | 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 |
| Deploys as | Hosted API (Streamable HTTP, SSE)confidence 0.90 | self-reported | docs.opensea.io | as of 2026-07-14 |
| Works with | ChatGPT, Cursor, Claude, Chorusconfidence 0.90 | self-reported | docs.opensea.io | as of 2026-07-14 |
| Sato Score | 67/100 (Medium)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 — as documented by the project, not run by us
Runtime: remote
curl -X POST https://api.opensea.io/api/v2/auth/keys # issue a free-tier API key
then add {"url": "https://mcp.opensea.io/mcp", "headers": {"X-API-KEY": "YOUR_KEY"}} to your MCP client config
{"mcpServers": {"OpenSea": {"url": "https://mcp.opensea.io/mcp", "headers": {"X-API-KEY": "YOUR_API_KEY"}}}}You supply: OpenSea API key (free tier, self-serve via POST /api/v2/auth/keys or opensea.io signup)
claude mcp add --transport http satohub-opensea-mcp https://mcp.opensea.io/mcp
A remote server: your client connects to the project's endpoint. 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-07-14. What a deploy spec is →
Tool inventory — 1 tool, probed live 2026-10-15
get_instant_api_key— Create a free OpenSea API key without signup or a wallet. Use it to bootstrap access when you don't have a key. Free-tier keys have lower rate limits and expire after 7 days. Pass the key in X-API-KEY
- Answers a handshake
- yes · 2026-10-15
- Answers a call
- not asked — every read-named tool also carries a mutating verb or names a credential
Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.
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.
Tool inventory history — 1 now, peak 1, since 2026-07-17
- 2026-09-23 0 → 1 +1 (get_instant_api_key)
Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.
Details
- Chains
- Multichain
- Agent types
- MCP Server, Data Provider
- Open source
- Unknown
- Pricing
- Free-tier API key instantly available (60/min read, 5/min write, 30-day expiry); higher limits via an OpenSea developer account
- Deploys as
- Hosted API (Streamable HTTP, SSE)
- Works with
- ChatGPT, Cursor, Claude, Chorus
- 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 OpenSea MCP fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to OpenSea MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Edited: mcp endpoint url
- Jul 14, 2026Auto-enriched: deployment options, supported integrations
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Zerion
ActiveWallet and DeFi data provider offering portfolio, positions, transactions, PnL, and prices across many chains, with an agent-accessible API.
Phantom MCP
ActivePhantom's MCP server that lets AI agents view addresses, sign transactions, swap, and transfer tokens across Solana, Ethereum, Bitcoin, and Sui.
OpenSea Agent Skill
ActiveOfficial OpenSea agent skill and MCP server letting AI agents query NFT/token data and execute marketplace operations such as listing, offers, and token swaps.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about OpenSea MCP
- Is OpenSea MCP open source?
- Unknown. Sato Hub has not found a public repository or a license statement for OpenSea MCP as of 2026-10-15.
- Which chains does OpenSea MCP support?
- OpenSea MCP lists support for Multichain as of 2026-10-15.
- Is OpenSea MCP still maintained?
- Sato Hub tracks no commit or release for OpenSea MCP; it cannot say whether it is maintained.
- How do I install or run OpenSea MCP?
- remote. Install: curl -X POST https://api.opensea.io/api/v2/auth/keys # issue a free-tier API key && then add {"url": "https://mcp.opensea.io/mcp", "headers": {"X-API-KEY": "YOUR_KEY"}} to your MCP client config. Entry: {"mcpServers": {"OpenSea": {"url": "https://mcp.opensea.io/mcp", "headers": {"X-API-KEY": "YOUR_API_KEY"}}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.opensea.io/mcp).
- Is OpenSea MCP verified on Sato Hub?
- Sato Hub holds one earned check for OpenSea MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 67 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. "OpenSea MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/opensea-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.