Port66
REMOTE · PORT66.XYZ
Search, price and buy authenticated luxury and collectibles, paying from any chain.
Available components
Last scanned (12 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1849 tokens (~205/item across 9 items; 9 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Tool “get_listing” rewrote its description, which is the text the model reads security
- Tool “make_offer” rewrote its description, which is the text the model reads security
- Tool “offer_status” rewrote its description, which is the text the model reads security
- Tool “payment_options” rewrote its description, which is the text the model reads security
- Tool “price_in_crypto” rewrote its description, which is the text the model reads security
- Tool “purchase_status” rewrote its description, which is the text the model reads security
- Tool “report_deposit” rewrote its description, which is the text the model reads security
- Tool “search_listings” rewrote its description, which is the text the model reads security
- Tool “start_purchase” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- Destructive annotations: pass → 100 functional
- “get_listing” reworded the description of “id” cosmetic
- “make_offer” reworded the description of “amount_usd” cosmetic
- “make_offer” reworded the description of “id” cosmetic
- “make_offer” reworded the description of “message” cosmetic
- “offer_status” reworded the description of “id” cosmetic
- “price_in_crypto” reworded the description of “chain” cosmetic
- “price_in_crypto” reworded the description of “id” cosmetic
- “price_in_crypto” reworded the description of “pay_with” cosmetic
- “purchase_status” reworded the description of “checkout_id” cosmetic
- “report_deposit” reworded the description of “checkout_id” cosmetic
- “report_deposit” reworded the description of “tx_hash” cosmetic
- “search_listings” reworded the description of “brand” cosmetic
- “search_listings” reworded the description of “category” cosmetic
- “search_listings” reworded the description of “limit” cosmetic
- “search_listings” reworded the description of “max_price” cosmetic
- “search_listings” reworded the description of “min_price” cosmetic
- “search_listings” reworded the description of “query” cosmetic
- “start_purchase” reworded the description of “chain” cosmetic
- “start_purchase” reworded the description of “id” cosmetic
- “start_purchase” reworded the description of “pay_with” cosmetic
- “start_purchase” reworded the description of “refund_to” cosmetic
- “start_purchase” reworded the description of “shipping_address” cosmetic
- 16 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 72
First indexed and scored.
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 21 Nov 2026 · Probed https://port66.xyz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=port66.xyz | CN=YR2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 2048 | SHA256-RSA | 67a6cf5bf65b734dcdf4d00f3d25bd7b3fa |
| SANs: port66.xyz | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 port66.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| port66.xyz. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://port66.xyz/api/mcp | Verified | 200 | |
| http (plaintext) | http://port66.xyz/api/mcp | HTTPS enforced | 308 | https://port66.xyz/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 Listing details ~155
Get the full record of one listing found with search_listings. Returns everything in the search result plus the seller's description, color, material, minimum offer, the on-chain provenance record (fingerprint and what it does and does not prove), when it was listed, and how to buy it: the checkout url and the payment methods it accepts. Use this before pricing or buying a piece. Fails with a clear message if the id does not exist or the piece is no longer for sale.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure'). |
No output schema declared.
No examples provided.
make_offer Make an offer ~171
Send the seller an offer below the listed price, with an optional note. The seller has 24 hours to accept, decline or counter; check with offer_status. If accepted, start_purchase uses the agreed price. Returns the offer id, its status and when it expires. Respect the listing's minimum_offer from get_listing. Requires a Port66 session.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | yes | The price offered for the piece, in US dollars, before shipping. |
| id | string | yes | The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure'). |
| message | string | – | A short, polite note to the seller (optional, up to a few sentences). |
No output schema declared.
No examples provided.
offer_status Offer status ~136
Check the signed-in buyer's latest offer on a listing made with make_offer. Returns the offer's amount in USD, its status (for example pending, accepted, declined or expired) and expiry, plus agreed_price_usd: the price start_purchase will charge if the seller accepted, otherwise null. Returns offer: null if the buyer has made no offer on this listing. Requires a Port66 session.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure'). |
No output schema declared.
No examples provided.
payment_options Payment options ~105
List the crypto assets and chains a buyer can pay with on Port66 (for example BTC on Bitcoin, SOL on Solana, ETH or USDC on Ethereum, Arbitrum or Base). Payments go through NEAR Intents and the seller always receives the exact price in USDC. Returns `available` (whether cross-chain payment is switched on) and `assets`, each with a symbol and chain to use as pay_with and chain in price_in_crypto. Takes no input.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_in_crypto Price in crypto ~251
Quote what a listing costs in a crypto asset right now. Asks NEAR Intents solvers how much of `pay_with` the buyer would send so the seller receives the listing's exact USD price (postage included) in USDC. Returns the piece, its USD price, the amount and asset to pay with its USD value, what the seller receives and on which chain, and the expected settlement time in seconds. Indicative and non-binding: it reserves nothing and charges nothing. Takes up to about 20 seconds. Fails with a clear message if the listing has no fixed price or NEAR Intents is unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Only needed when the asset exists on several chains: ETH and USDC on Ethereum, Arbitrum or Base, USDC also on NEAR. Omit it otherwise. |
| id | string | yes | The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure'). |
| pay_with | string | yes | The crypto asset the buyer pays with. payment_options lists which chains each one is accepted on. |
No output schema declared.
No examples provided.
purchase_status Purchase status ~138
Check a purchase started with start_purchase. Returns its state: awaiting_deposit (send the amount), deposit_seen, processing, paid (the order is recorded and the seller was paid), refunded (funds returned to refund_to), failed, expired (deadline passed without a deposit) or review (being checked by Port66). Also returns links to the buyer's payment and the seller's payout transactions and, once paid, the order_id. Poll every 15 to 30 seconds while the state is awaiting_deposit, deposit_seen or processing. Requires a Port66 session.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | The checkout_id returned by start_purchase. |
No output schema declared.
No examples provided.
report_deposit Report a deposit ~121
Optionally tell Port66 the transaction hash of the buyer's deposit for a purchase, so NEAR Intents spots the payment sooner. Not required: deposits are detected on their own. Does not move money or change the amount due. Returns the purchase's current state. Safe to call more than once. Requires a Port66 session.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | The checkout_id returned by start_purchase. |
| tx_hash | string | yes | The hash (transaction id) of the deposit the buyer sent, as shown by their wallet or a block explorer. |
No output schema declared.
No examples provided.
search_listings Search Port66 ~291
Find pieces for sale on Port66 (authenticated luxury, streetwear and collectibles). Use this first: every other listing tool needs an `id` from these results. Returns up to `limit` active listings, each with id, title, brand, category, condition, size, price in USD (null when the seller only takes offers), whether it accepts offers, shipping, authenticity level, seller, image_url and a port66.xyz url. All filters are optional; with none, returns the newest listings. Multi-word queries match listings containing those words, so 'kaws elmo' finds 'KAWS x Sesame Street Elmo'.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Only listings from this brand, e.g. 'Miu Miu' or 'Supreme'. Partial, case-insensitive match. |
| category | string | – | Only listings in this category, e.g. 'Bags', 'Sneakers' or 'Collectibles'. |
| limit | integer | – | How many listings to return, 1 to 20. Defaults to 10. |
| max_price | number | – | Highest listed price to include, in US dollars. |
| min_price | number | – | Lowest listed price to include, in US dollars. |
| query | string | – | Words to look for in the listing title, e.g. 'KAWS figure' or 'Chrome Hearts tee'. One to three words work best. |
No output schema declared.
No examples provided.
start_purchase Start a purchase ~311
Reserve a listing for the signed-in buyer and get a one-time NEAR Intents deposit address and the exact amount of `pay_with` to send. Nothing is charged by this call: the purchase completes only when the buyer's own wallet sends that exact amount to that address before the deadline. Returns a checkout_id, the deposit address, exact amount, asset, chain and the pay_before deadline. If the seller accepted the buyer's offer, the agreed price is used. Requires a Port66 session (Authorization: Bearer token from wallet sign-in). Then poll purchase_status until it is `paid`.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Only needed when the asset exists on several chains: ETH and USDC on Ethereum, Arbitrum or Base, USDC also on NEAR. Omit it otherwise. |
| id | string | yes | The listing's id, exactly as returned in the `id` field of search_listings results (a slug such as 'kaws-x-sesame-street-water-parade-elmo-figure'). |
| pay_with | string | yes | The crypto asset the buyer pays with. payment_options lists which chains each one is accepted on. |
| refund_to | string | yes | The buyer's own wallet address on the paying chain (for example a 0x address for Ethereum or Base, a Solana address for SOL). If the payment cannot complete, the funds are returned here. Never an exc… |
| shipping_address | object | yes | Where the piece is shipped. |
No output schema declared.
No examples provided.
How do I install the Port66 MCP server?
Port66 is a hosted endpoint at https://port66.xyz/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 · port66.xyz
claude mcp add --transport http xyz-port66-marketplace 'https://port66.xyz/api/mcp'
What is the Port66 MCP server?
Port66 is an MCP server listed in the public MCP registry as xyz.port66/marketplace. Search, price and buy authenticated luxury and collectibles, paying from any chain. This page covers its hosted endpoint (https://port66.xyz/api/mcp).
Is the Port66 MCP server safe to use?
Port66 scores 74 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 Port66 MCP server expose?
Port66 exposes 9 tools: search_listings, get_listing, payment_options, price_in_crypto, start_purchase, and 4 more. Their descriptions and schemas cost roughly 1,679 tokens of context every time the server is loaded.
Does the Port66 MCP server require authentication?
No. We connected to Port66 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Port66 MCP server still maintained?
Port66 is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Port66 MCP server?
VerifyMCP ran 13 checks on Port66, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.