com.market0x/marketplace
REMOTE · WWW.MARKET0X.COM · SCANNED SEP 20
Buy, sell and bid on vote-escrow NFTs and .base.eth names. Non-custodial, settles on Seaport.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1493 tokens (~114/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management69
- Stability check failed: schema churn in the 25 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "unsubscribe_notifications" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 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
How do I install the com.market0x/marketplace MCP server?
com.market0x/marketplace is a hosted endpoint at https://www.market0x.com/api/mcp, 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 · www.market0x.com
claude mcp add --transport http com-market0x-marketplace 'https://www.market0x.com/api/mcp'
{
"mcpServers": {
"com-market0x-marketplace": {
"url": "https://www.market0x.com/api/mcp"
}
}
} {
"servers": {
"com-market0x-marketplace": {
"type": "http",
"url": "https://www.market0x.com/api/mcp"
}
}
} [mcp_servers.com-market0x-marketplace] url = "https://www.market0x.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-market0x-marketplace": {
"type": "remote",
"url": "https://www.market0x.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-market0x-marketplace --url 'https://www.market0x.com/api/mcp' --transport streamable-http
mcp_servers:
com-market0x-marketplace:
url: "https://www.market0x.com/api/mcp" {
"McpServers": {
"com-market0x-marketplace": {
"Transport": "http",
"Url": "https://www.market0x.com/api/mcp"
}
}
} assistant mcp add com-market0x-marketplace -t streamable-http -u 'https://www.market0x.com/api/mcp'
{
"mcpServers": {
"com-market0x-marketplace": {
"type": "http",
"url": "https://www.market0x.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 −1
- Stability: 0.77 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “prepare_finalize” was removed ▼ security
- Tool “search_names” was removed ▼ security
- Tool “prepare_listing” rewrote its description, which is the text the model reads security
- Tool “prepare_offer” rewrote its description, which is the text the model reads security
- Tool coverage: 52% → 42% ▼ functional
- Schema quality: 130 → 114 ▲ functional
- “get_listings” reworded the description of “minDiscountPct” cosmetic
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://www.market0x.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.market0x.com | CN=YR1,O=Let's Encrypt,C=US | 9 Aug 2026 | 7 Nov 2026 | RSA 2048 | SHA256-RSA | 605dbd705fd691b05d983776de2f6176cac |
| SANs: www.market0x.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.market0x.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| market0x.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.market0x.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.market0x.com/api/mcp | HTTPS enforced | 308 | https://www.market0x.com/api/mcp |
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 →
get_listing_details ~46
Full detail for one order including a FRESH live-contents snapshot (principal, claimable rewards, voting/earning power, as_of_block).
| Name | Type | Req | Description |
|---|---|---|---|
| orderHash | string | yes | – |
No output schema declared.
No examples provided.
get_listings ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | number | – | – |
| marketId | string | yes | market id, e.g. 'vehydx' |
| minDiscountPct | number | – | only return orders at >= this discount %. IGNORED on markets whose asset has no priced underlying, where there is nothing to compare the ask against — the response says so in `note` rather than retur… |
| nameContains | string | – | case-insensitive substring match on the listing's label (the name on name markets, e.g. 'alice'; 'veAERO #123' elsewhere) |
No output schema declared.
No examples provided.
get_orders ~54
List orders created by an address (its listings, auctions, offers). Status is reconciled by the background worker — treat as advisory until checked at fill.
| Name | Type | Req | Description |
|---|---|---|---|
| offerer | string | yes | – |
| status | string | – | – |
No output schema declared.
No examples provided.
get_owned_positions ~46
List the positions an address owns in a market, with listability (voted/attached positions can't transfer).
| Name | Type | Req | Description |
|---|---|---|---|
| marketId | string | yes | – |
| owner | string | yes | – |
No output schema declared.
No examples provided.
get_recent_trades ~108
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| marketId | string | yes | – |
No output schema declared.
No examples provided.
list_micro_markets ~25
List the markets this marketplace facilitates (asset, chain, currencies, fee).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_subscriptions ~31
List a wallet's notification subscriptions (webhook URLs redacted to origin).
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
prepare_cancel ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| orderHash | string | yes | – |
No output schema declared.
No examples provided.
prepare_listing ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ask | string | – | listing: price the seller nets — must be positive |
| currencySymbol | string | yes | one of the market's settlementCurrencies (see list_micro_markets) |
| durationDays | number | – | – |
| endAsk | string | – | dutch_auction: floor price (must be below the start) |
| kind | string | yes | – |
| marketId | string | yes | – |
| name | string | – | name markets only, e.g. 'alice' or 'alice.base.eth' — tokenId is derived |
| seller | string | yes | – |
| startAsk | string | – | dutch_auction: starting (high) price |
| tokenId | string | – | required for token markets (e.g. vehydx) |
No output schema declared.
No examples provided.
prepare_offer ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | yes | 0x address that will sign and fund the offer |
| currencySymbol | string | yes | one of the market's settlementCurrencies (see list_micro_markets) |
| durationDays | number | – | – |
| marketId | string | yes | – |
| name | string | – | name markets only, e.g. 'alice' or 'alice.base.eth' — tokenId is derived |
| offerAmount | string | yes | human amount the seller nets, e.g. '750' — must be positive |
| tokenId | string | – | required for token markets (e.g. vehydx) |
No output schema declared.
No examples provided.
prepare_purchase ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| orderHash | string | yes | – |
No output schema declared.
No examples provided.
subscribe_notifications ~274
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))).
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | yes | chain the wallet signs on; it is part of the signed message |
| channel | string | yes | – |
| events | array | yes | – |
| savedSearch | object | – | – |
| signature | string | – | EIP-191 signature of the canonical message; omit to receive the message to sign |
| timestamp | number | yes | unix seconds; must be within 10 minutes of now |
| wallet | string | yes | – |
| webhookUrl | string | – | https URL; required for the webhook channel |
No output schema declared.
No examples provided.
unsubscribe_notifications ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | yes | chain the wallet signs on; it is part of the signed message |
| signature | string | – | – |
| subscriptionId | string | yes | – |
| timestamp | number | yes | – |
| wallet | string | yes | – |
No output schema declared.
No examples provided.
What is the com.market0x/marketplace MCP server?
com.market0x/marketplace is an MCP server listed in the public MCP registry as com.market0x/marketplace. Buy, sell and bid on vote-escrow NFTs and .base.eth names. Non-custodial, settles on Seaport. This page covers its hosted endpoint (https://www.market0x.com/api/mcp).
Is the com.market0x/marketplace MCP server safe to use?
com.market0x/marketplace scores 73 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 com.market0x/marketplace MCP server expose?
com.market0x/marketplace exposes 13 tools: list_micro_markets, get_listings, get_listing_details, get_recent_trades, prepare_purchase, and 8 more. Their descriptions and schemas cost roughly 1,493 tokens of context every time the server is loaded.
Does the com.market0x/marketplace MCP server require authentication?
No. We connected to com.market0x/marketplace without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.market0x/marketplace MCP server still maintained?
com.market0x/marketplace is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.