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.

Escrova

REMOTE · WWW.ESCROVA.IO

Search Amazon, eBay, Walmart and more and compare prices. Agents can search, not buy.

Available components

65 Trust /100

Last scanned (1 day ago)

Scores higher than 45% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

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 Security66
  • 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 8 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1199 tokens (~149/item across 8 items; 8 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 39% 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 8 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 4 Nov 26 65

    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 4 Nov 2026 · Probed https://www.escrova.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=escrova.io CN=WE1,O=Google Trust Services,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA256 ee0368d941eac6a913ed48ceefac07a8
SANs: escrova.io, *.escrova.io
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 secure

Validation of www.escrova.io. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
escrova.io. present 2371 13 Verified
www.escrova.io. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains
content-security-policy default-src 'none';frame-ancestors 'none';object-src 'none';base-uri 'none';form-action 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=("https://in.sumsub.com" "https://api.sumsub.com"), microphone=(), geolocation=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.escrova.io/api/mcp Verified 200
http (plaintext) http://www.escrova.io/api/mcp HTTPS enforced 308 https://www.escrova.io/api/mcp
MCP tools · 8 exposed · ~1,087 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_category ~233

Narrow towards a purchase without inventing keywords. One call returns children[] and childrenDeep[] with estimated counts, brands[] each with an engineParam you can pass straight back to search_products.engineParam, the shop's own facets[], aspectTiles[], siblings[], related[] and a deals[] rail. GET /api/agent/browse/tree/<slug>, or GET /api/agent/browse/tree/<slug>/<nodeId> for any category under a department. No wallet and no signature. contentAt is when those deal prices were read: send it as a candidate's priceAt to compare_landed_cost, which is the shortlist this call is meant to fill. Counts are estimates and countScope says so. A shelf already read answers from cache; a cold one costs one call against the catalogue quota shared with shoppers, so read the shelf you want rather than walking the tree.

NameTypeReqDescription
nodeIdstring–A category id under that department, from children[].id or childrenDeep[].id. Omit for the department itself.
slugstringyesThe `slug` field of a department from list_categories.

No output schema declared.

No examples provided.

get_deals ~166

For a "find something on offer" task. GET /api/agent/browse/deals?tab=<tab>, where tab is markdowns, refurbished, top-rated, brands, or door:<slug> for one department. No wallet and no signature. Every item carries cachedAt, which is when that price was true: pass it as a candidate's priceAt to compare_landed_cost. A selection over rows this site has already cached, so it costs no catalogue call. An unknown tab is refused with 400 rather than guessed at. A sticker discount is not a cheaper order: rank with compare_landed_cost before you quote.

NameTypeReqDescription
tabstringyesmarkdowns, refurbished, top-rated, brands, or door:<slug> with a slug from list_categories.

No output schema declared.

No examples provided.

get_directory ~101

Every department, the groups under it and the links under those, for picking a shelf in one read rather than walking down to it. GET /api/agent/browse/directory. No wallet and no signature. Built ONLY from rows already cached, so it costs no catalogue call at all and a picture or count nobody has fetched yet comes back null rather than being fetched for you. Prefer this over repeated get_category calls when you are still deciding where to look.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_fees ~41

The current fee schedule and delivery rates, so a total can be explained before anyone pays it. GET /api/config/fees. No wallet and no signature.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_prices ~41

Current USD prices of the coins shown on Escrova. GET /api/prices. No wallet and no signature. Checkout on this deployment takes USDC only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_terms ~59

Returns the current Terms of Service and Privacy Policy version and document hash. These are the exact values accept_terms will record; they are read server-side and never taken from your request. GET /api/agent/legal/terms. No wallet and no signature.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_categories ~117

Start a shopping task here instead of guessing search words. Returns the sixteen departments, each with the slug get_category takes and a picture. A keyword search is one guess at what somebody meant; a department is the shop's own shelf, and get_category on one hands you the brands, the filters and a page of listings in a single call. GET /api/agent/browse/categories. No wallet and no signature. Served from cache; a department whose picture has gone cold costs one call against the catalogue quota this site shares with its shoppers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_products ~329

Search products across the marketplaces Escrova can actually buy from today. Six sources are searchable: amazon, ebay, walmart, bestbuy, homedepot, wayfair, or "all". GET /api/products/search. No wallet and no signature. Send q, cat, or both; page and every selected filter are preserved together. A brands[].engineParam returned by get_category goes into engineParam here and is sent as the typed eBay aspect filter, while Google refinements use shoprs. The REST pagination and degraded-source metadata are returned unchanged. A search is one guess at what somebody meant and it spends a paid provider call; when you know roughly what department a thing is in, list_categories and get_category narrow further for less.

NameTypeReqDescription
catstring–Department slug, category id, or <id>-<slug> returned by get_category.
ebayAspectFilterstring––
ebayCategoryIdstring––
ebayConditionIdsstring––
engineParamstring–A brands[].engineParam from get_category; sent only as ebayAspectFilter.
freeShippingboolean––
limitinteger––
maxPricenumber––
minPricenumber––
minRatingnumber––
pageinteger––
qstring–What to search for. Optional when cat is supplied.
shoprsstring–A Google filter option whose engineParamType is shoprs.
sortstring––
sourcestring––

No output schema declared.

No examples provided.

Install

How do I install the Escrova MCP server?

Escrova is a hosted endpoint at https://www.escrova.io/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.escrova.io

# add to Claude Code
claude mcp add --transport http io-escrova-escrova 'https://www.escrova.io/api/mcp'
Common questions

What is the Escrova MCP server?

Escrova is an MCP server listed in the public MCP registry as io.escrova/escrova. Search Amazon, eBay, Walmart and more and compare prices. Agents can search, not buy. This page covers its hosted endpoint (https://www.escrova.io/api/mcp).

Is the Escrova MCP server safe to use?

Escrova scores 65 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 Escrova MCP server expose?

Escrova exposes 8 tools: search_products, get_fees, get_prices, get_terms, list_categories, and 3 more. Their descriptions and schemas cost roughly 1,087 tokens of context every time the server is loaded.

Does the Escrova MCP server require authentication?

No. We connected to Escrova without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Escrova MCP server still maintained?

Escrova is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.