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.

iEscrow Marketplace (read-only)

REMOTE · API.IESCROW.IO

Search iEscrow: products, services and P2P crypto offers held in escrow. Read-only, no login.

Available components

64 Trust /100

Last scanned (17 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1488 tokens (~297/item across 5 items; 5 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 62

    First indexed and scored.

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 21 Nov 2026 · Probed https://api.iescrow.io/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=iescrow.io CN=YE1,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA384 5364a248e18279f31b05ff9e133c9a8c46a
SANs: *.iescrow.io, iescrow.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.iescrow.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
iescrow.io. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.iescrow.io/mcp/public Verified 200
http (plaintext) http://api.iescrow.io/mcp/public Inconclusive 405
MCP tools · 5 exposed · ~1,026 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
get_product_or_service ~110

Full detail of one listing from search_products_and_services plus a quote: how much crypto a buyer would lock to buy it right now (price in USD converted at the current rate, plus iEscrow's standard fee) and how long the seller has to deliver before the escrow releases by itself. No account needed. The purchase itself is made by the person at the listing's url.

NameTypeReqDescription
listing_id–yeslisting_id or public_id from search_products_and_services
quantityinteger––

No output schema declared.

No examples provided.

get_quote ~236

Best live offers on the iEscrow P2P marketplace for buying or selling crypto with fiat money, for the given crypto amount: price with the maker's margin, what the user would pay or receive all-in (platform fee included), whether it is instant and the accepted payment methods. No account needed to look. In every trade the crypto is locked in escrow BEFORE the fiat is paid, and released when the seller confirms the payment arrived. Taking an offer needs an iEscrow account: on the web at the marketplace, or with the agent connected to the full server.

NameTypeReqDescription
amountnumberyesAmount in CRYPTO units
cryptostringyesCrypto symbol, e.g. USDT, BTC, ETH
fiatstringyesFiat ISO code, e.g. ARS, USD, BRL, EUR
limitinteger––
payment_methodstring–Optional payment method name to filter (e.g. 'Mercado Pago', 'PIX')
sidestringyesbuy = the user pays fiat and receives crypto; sell = the user delivers crypto and receives fiat

No output schema declared.

No examples provided.

get_seller_profile ~77

The real track record of an iEscrow account: completed trades, cancellations at fault, dispute rate, average star rating and whether their identity is verified. Use the seller.user_id from search_products_and_services. No account needed. There is no invented score: what you get is what happened.

NameTypeReqDescription
user_idintegeryes–

No output schema declared.

No examples provided.

get_swap_quote ~195

Best live offers on the iEscrow marketplace to swap one crypto for another, for the given amount. Both legs are held in escrow, so there is no payment account and no bank involved. The platform fee is charged on EACH leg separately, so the reply states what the user would deliver fee included and what they would receive net. Give either give_amount or get_amount, not both. No account needed to look; taking an offer needs an iEscrow account. For crypto against government money use get_quote instead.

NameTypeReqDescription
get_amountnumber–Amount the user wants to receive. Give this OR give_amount.
get_currencystringyesCrypto the user receives, e.g. BTC
give_amountnumber–Amount the user wants to deliver. Give this OR get_amount.
give_currencystringyesCrypto the user delivers, e.g. USDT
limitinteger––

No output schema declared.

No examples provided.

search_products_and_services ~408

Searches iEscrow's public catalog of physical products and services sold for crypto, with the seller's REAL reputation on each result (identity verified, completed trades, success and dispute rates, star rating). No account needed. Filter by text, price range in USD, category, condition, country it ships to, and minimum seller reputation. Each result carries two different clocks: ships_within_days is how long the seller has to hand the parcel to the courier (miss it and the buyer is refunded automatically) and delivery_days is how long it then takes to arrive. Each result has `url`, the page on iescrow.io where a person buys it: the buyer's crypto is held by iEscrow and released only when the buyer confirms delivery. Empty results mean nobody is selling that right now; never invent listings.

NameTypeReqDescription
categorystring–One of the categories returned in `categories`
conditionstring–Products only, best to worst: new (sealed), like_new, open_box, refurbished, used
identity_verified_onlyboolean–Only sellers with verified identity (KYC). Recommended for anything over a few hundred dollars.
kindstring––
limitinteger––
max_price_usdnumber––
min_completed_tradesinteger–Minimum completed trades of the seller
min_price_usdnumber––
min_ratingnumber–Minimum average star rating of the seller (sellers with no ratings yet are excluded)
offsetinteger–Skip this many results, to page through a total bigger than limit
querystring–Free text, e.g. 'macbook pro m3'
ships_tostring–ISO-2 country the buyer is in, e.g. AR, US. Products that ship worldwide always match.
sortstring–Default newest. 'reputation' puts verified sellers with the most completed trades first.

No output schema declared.

No examples provided.

Install

How do I install the iEscrow Marketplace (read-only) MCP server?

iEscrow Marketplace (read-only) is a hosted endpoint at https://api.iescrow.io/mcp/public, 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 · api.iescrow.io

# add to Claude Code
claude mcp add --transport http iescrow-marketplace 'https://api.iescrow.io/mcp/public'
Common questions

What is the iEscrow Marketplace (read-only) MCP server?

iEscrow Marketplace (read-only) is an MCP server listed in the public MCP registry as io.github.iEscrow/marketplace. Search iEscrow: products, services and P2P crypto offers held in escrow. Read-only, no login. This page covers its hosted endpoint (https://api.iescrow.io/mcp/public).

Is the iEscrow Marketplace (read-only) MCP server safe to use?

iEscrow Marketplace (read-only) scores 64 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 iEscrow Marketplace (read-only) MCP server expose?

iEscrow Marketplace (read-only) exposes 5 tools: search_products_and_services, get_product_or_service, get_seller_profile, get_quote, get_swap_quote. Their descriptions and schemas cost roughly 1,026 tokens of context every time the server is loaded.

Does the iEscrow Marketplace (read-only) MCP server require authentication?

No. We connected to iEscrow Marketplace (read-only) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the iEscrow Marketplace (read-only) MCP server still maintained?

iEscrow Marketplace (read-only) 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 iEscrow Marketplace (read-only) MCP server?

VerifyMCP ran 12 checks on iEscrow Marketplace (read-only), covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about iEscrow Marketplace (read-only): HTTPS. 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.