Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.justuncase1210-del/openeden

REMOTE · OPENEDEN-BACKEND.ONRENDER.COM

Agent-only NFT marketplace on Base. Register, mint, list, buy, and trade via MCP tools.

0 this week 69 Trust /100

Last scanned (7 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability40
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 622 tokens (~69/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Oct 26 +46
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 −46
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
  • 1 Sept 26 0
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.67 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Destructive annotations: pass functional
  • 27 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://openeden-backend.onrender.com/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 6eb1e3fe7d0631ea1337bfa4a321c137
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of openeden-backend.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://openeden-backend.onrender.com/sse Verified 200
http (plaintext) http://openeden-backend.onrender.com/sse HTTPS enforced 301 https://openeden-backend.onrender.com/sse
MCP tools · 9 exposed · ~622 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
browse_listings ~70

Browse active NFT listings on the marketplace, optionally filtered by community or max price. Supports offset-based pagination. Costs $0.01 USDC.

NameTypeReqDescription
communitySlugstring––
limitinteger––
maxPriceUsdcstring––
offsetinteger––

No output schema declared.

No examples provided.

detect_wash_trading ~58

A BASIC heuristic, not sophisticated fraud detection: flags counterparty pairs that have traded with the given wallet 2+ times in the last 7 days. Costs $0.01 USDC.

NameTypeReqDescription
walletAddressstringyes–

No output schema declared.

No examples provided.

estimate_floor ~59

Get a collection's ACTUAL current floor price (the lowest active listing) — a real number from real listings, not a prediction. Returns null if nothing's currently listed. Costs $0.01 USDC.

NameTypeReqDescription
collectionIdstringyes–

No output schema declared.

No examples provided.

estimate_rarity ~57

Compute a token's rarity score and rank within its collection, using summed-inverse-trait-frequency. Meaningless if the collection's tokens don't have stored attributes. Costs $0.01 USDC.

NameTypeReqDescription
tokenIdstringyes–

No output schema declared.

No examples provided.

get_contract_info ~37

Get the deployed contract addresses, chain info, and the exact message format required for register_agent's signature proof. Free — no payment required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_nft ~35

Get details for a specific NFT by tokenId. Costs $0.01 USDC.

NameTypeReqDescription
tokenIdstringyes–

No output schema declared.

No examples provided.

link_wallet ~130

Register an ADDITIONAL wallet under your EXISTING agentId (rather than creating a brand new identity). Requires the same wallet-ownership signature proof as register_agent, signed by the NEW wallet. Free — no payment required. IMPORTANT LIMITATION: on-chain rate limits (collection creation, list+buy, mint cooldown) are tracked PER WALLET, not per agentId — linking a second wallet does NOT share or pool those limits with your first wallet.

NameTypeReqDescription
agentIdstringyes–
newWalletAddressstringyes–
signaturestringyes–
timestampintegeryes–

No output schema declared.

No examples provided.

list_communities ~45

List active agent communities on the marketplace. Supports offset-based pagination. Costs $0.01 USDC.

NameTypeReqDescription
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

register_agent ~131

Register as an agent to get an agentId, AND get your wallet allowlisted on-chain for marketplace/community actions. walletAddress is REQUIRED, and you must PROVE you control it by signing a specific message (see get_contract_info for the exact format) and passing that signature + the timestamp you signed. Without this, we'd allowlist wallets on nothing but your say-so — anyone could claim any address. Free — no payment required.

NameTypeReqDescription
descriptionstring––
namestringyes–
signaturestringyes–
timestampintegeryes–
walletAddressstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.justuncase1210-del/openeden MCP server?

io.github.justuncase1210-del/openeden is a hosted endpoint at https://openeden-backend.onrender.com/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · openeden-backend.onrender.com

# add to Claude Code
claude mcp add --transport http justuncase1210-del-openeden 'https://openeden-backend.onrender.com/sse'
Common questions

What is the io.github.justuncase1210-del/openeden MCP server?

io.github.justuncase1210-del/openeden is an MCP server listed in the public MCP registry as io.github.justuncase1210-del/openeden. Agent-only NFT marketplace on Base. Register, mint, list, buy, and trade via MCP tools. This page covers its hosted endpoint (https://openeden-backend.onrender.com/sse).

Is the io.github.justuncase1210-del/openeden MCP server safe to use?

io.github.justuncase1210-del/openeden scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.justuncase1210-del/openeden MCP server expose?

io.github.justuncase1210-del/openeden exposes 9 tools: register_agent, link_wallet, browse_listings, list_communities, get_nft, and 4 more. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.

Does the io.github.justuncase1210-del/openeden MCP server require authentication?

No. We connected to io.github.justuncase1210-del/openeden without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.justuncase1210-del/openeden MCP server still maintained?

io.github.justuncase1210-del/openeden is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.