marketplace MCP server
com.market0x/marketplacemarket0x.comstreamable-httpv0.1.0Scanned
Buy, sell and bid on vote-escrow NFTs and .base.eth names. Non-custodial, settles on Seaport.
13 tools: 2 can delete or cancel things, 1 do something that can't be undone, 3 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the marketplace MCP server can do
The marketplace MCP server is published by market0x.com, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (2 tools: prepare_cancel and unsubscribe_notifications), do things that cannot be undone, such as sending, paying or publishing (prepare_purchase) and create or change data (3 tools: prepare_offer, prepare_listing and subscribe_notifications). 7 tools only read.
1 tool can send data out of your system (subscribe_notifications).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Deletes or cancels 2Claude Code: deny
prepare_cancelPrepare the on-chain Seaport cancel transaction for an active order.No findings
Why it is in this group
- The name "prepare_cancel" says "cancel": a word for removing or ending something.
Description, as the server wrote it Prepare the on-chain Seaport cancel transaction for an active order. Only the order's offerer can execute it (Seaport enforces msg.sender == offerer), so the calldata is safe to return. After it confirms, POST { txHash } to the confirm endpoint to update the book.
unsubscribe_notificationsDelete a notification subscription.No findings
Why it is in this group
- The name "unsubscribe_notifications" says "unsubscribe": a word for a change.
- The description's first verb is "delete": a word for removing or ending something.
Description, as the server wrote it Delete a notification subscription. Two-step like subscribe_notifications: call without `signature` to get the message to sign. `chainId` is signed over and verified on that chain. Signed messages are single-use.
Can't be undone 1Claude Code: ask
prepare_purchasePrepare the non-custodial transaction package to BUY a listing (or accept an offer): ordered approvals + Seaport fulfillOrder calldata + a fresh contents snapshot.No findings
Why it is in this group
- The name "prepare_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Prepare the non-custodial transaction package to BUY a listing (or accept an offer): ordered approvals + Seaport fulfillOrder calldata + a fresh contents snapshot. prepared.summary quotes the CURRENT price (Dutch auctions interpolate, asOf says when); the approval grants approveBaseUnits — slightly above the quote on a decaying order, never above maxTotalBaseUnits — and Seaport charges the exact interpolated amount at fill. On auctions, prepared.cleanup is an optional post-settlement tx that zeroes the residual allowance. The agent's own wallet signs and submits — this never signs or holds keys.
Changes things 3Claude Code: ask
prepare_listingPrepare a SELL listing or Dutch auction.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prepare a SELL listing or Dutch auction. Verifies the seller OWNS the position and it's transferable (not voted/attached), builds the Seaport order with the Interface fee injected by the server, and returns the one-time NFT approval + EIP-712 typed data to sign. Never signs or holds keys.
prepare_offerPrepare a BID/offer on a position: returns the Seaport order to sign (EIP-712), the currency approval needed, and how to submit it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prepare a BID/offer on a position: returns the Seaport order to sign (EIP-712), the currency approval needed, and how to submit it. The agent reads its Seaport counter, signs, and POSTs the signed order — settlement stays on Seaport. The buyer wallet must hold the offer's outlay (price + its fee share) when it submits; an unfunded offer is rejected (insufficient_balance), and one that later loses its funds or allowance is hidden from the book until they return.
subscribe_notificationsSubscribe a wallet to push notifications (order_filled / offer_received / saved_search) via an HMAC-signed webhook — the agent-native alternative to polling.Can send data outNo findings
Why it is in this group
- The name "subscribe_notifications" says "subscribe": a word for a change.
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
- outboundThe input takes a URL (input.webhookUrl): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Subscribe a wallet to push notifications (order_filled / offer_received / saved_search) via an HMAC-signed webhook — the agent-native alternative to polling. Two-step: call WITHOUT `signature` to get the exact message to sign (EIP-191 personal_sign), then call again WITH the signature. `chainId` is signed over and the signature is verified on THAT chain, so pass the chain the wallet actually signs on (smart-wallet signatures do not validate cross-chain). Each signed message is SINGLE-USE: resending the same body returns 409 replayed_signature — retry with a fresh timestamp and a new signature. The response includes the webhook HMAC secret ONCE (verify x-market0x-signature = hex(HMAC-SHA256(rawBody, secret))).
Only reads 7Show 7 read-only tools
get_listing_detailsFull detail for one order including a FRESH live-contents snapshot (principal, claimable rewards, voting/earning power, as_of_block).No findings
Why it is in this group
- The name "get_listing_details" says "get": a word for reading.
Description, as the server wrote it Full detail for one order including a FRESH live-contents snapshot (principal, claimable rewards, voting/earning power, as_of_block).
get_listingsActive listings/auctions for a market.No findings
Why it is in this group
- The name "get_listings" says "get": a word for reading.
Description, as the server wrote it Active listings/auctions for a market. Each row carries the ask and the position's underlying contents priced at current market (published formula: /docs#data-sources), plus discountPct (the difference between them). Sorted by discount percentage, descending.
get_ordersList orders created by an address (its listings, auctions, offers).No findings
Why it is in this group
- The name "get_orders" says "get": a word for reading.
Description, as the server wrote it List orders created by an address (its listings, auctions, offers). Status is reconciled by the background worker — treat as advisory until checked at fill.
get_owned_positionsList the positions an address owns in a market, with listability (voted/attached positions can't transfer).No findings
Why it is in this group
- The name "get_owned_positions" says "get": a word for reading.
Description, as the server wrote it List the positions an address owns in a market, with listability (voted/attached positions can't transfer).
get_recent_tradesRecently settled sales for a market.No findings
Why it is in this group
- The name "get_recent_trades" says "get": a word for reading.
Description, as the server wrote it Recently settled sales for a market. `amount` is the EXACT settled total (incl. fee) from the on-chain fill where the indexer recorded it, with `settledAt` the block time and `exact: true`; otherwise it falls back to the listed ask with `exact: false` (a decayed Dutch auction settles BELOW its listed amount, so treat inexact rows as an upper bound).
list_micro_marketsList the markets this marketplace facilitates (asset, chain, currencies, fee).No findings
Why it is in this group
- The name "list_micro_markets" says "list": a word for reading.
Description, as the server wrote it List the markets this marketplace facilitates (asset, chain, currencies, fee).
list_subscriptionsList a wallet's notification subscriptions (webhook URLs redacted to origin).No findings
Why it is in this group
- The name "list_subscriptions" says "list": a word for reading.
Description, as the server wrote it List a wallet's notification subscriptions (webhook URLs redacted to origin).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:42 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (2 destructive, 1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.market0x.com/api/mcp: tools/list returned 13 tools to an anonymous client, including prepare_cancel (destructive), unsubscribe_notifications (destructive), prepare_purchase (irreversible), prepare_offer (write), prepare_listing (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:prepare_listingChanges thingsinputSchema
- Changed:prepare_offerChanges thingsdescriptioninputSchema
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http marketplace https://www.market0x.com/api/mcpclaude mcp add --transport http marketplace https://www.market0x.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__marketplace__list_micro_markets",
"mcp__marketplace__get_listings",
"mcp__marketplace__get_listing_details",
"mcp__marketplace__get_recent_trades",
"mcp__marketplace__get_orders",
"mcp__marketplace__get_owned_positions",
"mcp__marketplace__list_subscriptions"
],
"ask": [
"mcp__marketplace__prepare_purchase",
"mcp__marketplace__prepare_offer",
"mcp__marketplace__prepare_listing",
"mcp__marketplace__subscribe_notifications"
],
"deny": [
"mcp__marketplace__prepare_cancel",
"mcp__marketplace__unsubscribe_notifications"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as marketplace. Review it before you use it.
Capability tags behind 1 rule
- mcp__marketplace__subscribe_notifications outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.market0x/marketplace/verify?hash=967cd54f3fec60022b7824b315b1df90405ec6114a176c0afceb8bf8dca70985" | jq -e '.changed == false'Pinned hash 967cd54f3fec, from Nov 10, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.market0x/marketplace/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.market0x/marketplace)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:58 UTC.
marketplace MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the marketplace MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the marketplace MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: prepare_cancel and unsubscribe_notifications.
Can the marketplace MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: prepare_purchase.
What tools does the marketplace MCP server have?
- 13 tools: 2 destructive, 1 irreversible, 3 write, 7 read. prepare_cancel, unsubscribe_notifications, prepare_purchase, prepare_offer, prepare_listing, subscribe_notifications, list_micro_markets, get_listings and 5 more.
Does the marketplace MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the marketplace MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): subscribe_notifications.
Has the marketplace MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.