Mercantry Registry
REMOTE · MERCANTRY.ORG · SCANNED SEP 25
Agent-native registry: 168k+ real restaurants in LA, Hong Kong & Tokyo. Unranked, honest signals.
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 Security57
- 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 9 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
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1570 tokens (~174/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 49% 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 9 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
How do I install the Mercantry Registry MCP server?
Mercantry Registry is a hosted endpoint at https://mercantry.org/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 · mercantry.org
claude mcp add --transport http org-mercantry-registry 'https://mercantry.org/mcp'
{
"mcpServers": {
"org-mercantry-registry": {
"url": "https://mercantry.org/mcp"
}
}
} {
"servers": {
"org-mercantry-registry": {
"type": "http",
"url": "https://mercantry.org/mcp"
}
}
} [mcp_servers.org-mercantry-registry] url = "https://mercantry.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-mercantry-registry": {
"type": "remote",
"url": "https://mercantry.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-mercantry-registry --url 'https://mercantry.org/mcp' --transport streamable-http
mcp_servers:
org-mercantry-registry:
url: "https://mercantry.org/mcp" {
"McpServers": {
"org-mercantry-registry": {
"Transport": "http",
"Url": "https://mercantry.org/mcp"
}
}
} assistant mcp add org-mercantry-registry -t streamable-http -u 'https://mercantry.org/mcp'
{
"mcpServers": {
"org-mercantry-registry": {
"type": "http",
"url": "https://mercantry.org/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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 25 Sept 2026 · Probed https://mercantry.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mercantry.org | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5b4d33c6209251acfe0c01a7c7f00d3e376 |
| SANs: mercantry.org | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mercantry.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| mercantry.org. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mercantry.org/mcp | Verified | 200 | |
| http (plaintext) | http://mercantry.org/mcp | HTTPS enforced | 301 | https://mercantry.org/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 →
cancel_booking Cancel a booking ~69
Cancel a booking in any non-terminal state, or a confirmed reservation (the registry notifies the merchant). Cancellation is mandatory when the human no longer wants the table — no-shows destroy merchant trust and are tracked per developer key.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
get_availability Get availability (honest v1 behavior) ~64
V1 does NOT hold live table availability — availability is checked on the phone call at booking time. This tool returns the merchant's reservation policy, structured hours, and holiday exceptions so you can pick a plausible time before calling place_booking.
| Name | Type | Req | Description |
|---|---|---|---|
| merchant_id | string | yes | – |
No output schema declared.
No examples provided.
get_booking_status Get booking status ~106
State machine position for a booking: pending → queued → in_progress → confirmed | failed | needs_input (plus cancelled). Includes structured details on confirmation (confirmed_time, confirmation_code, merchant_instructions), structured failure reason (no_answer | fully_booked | closed | policy_mismatch | merchant_declined | bad_data), or needs_input options awaiting your decision. include_events=true returns the full audit log.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | – |
| include_events | boolean | – | – |
No output schema declared.
No examples provided.
get_merchant Get merchant (full signal dump) ~63
Every field the registry holds on one merchant: schema fields, structured hours, raw feedback history, platform-observed operational stats, and per-field provenance with timestamps. Maximal data, zero opinion — the registry never scores or ranks.
| Name | Type | Req | Description |
|---|---|---|---|
| merchant_id | string | yes | – |
No output schema declared.
No examples provided.
get_registry_meta Get registry metadata ~60
Evaluate the registry itself: per-city coverage (with each city's IANA timezone), merchant/bookable counts, verification and freshness stats, feedback corpus size, schema version, and the documented deterministic ordering rule. Honest by design — including how stale the data is.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
modify_booking Modify a booking / resolve needs_input ~143
Amend a booking before or after the call. For a booking in needs_input: pass accept_option_index to take one of the merchant's offered times (confirms immediately), or pass a new datetime/party_size to re-queue an amended request. Modifying an already-confirmed booking cancels it and books the new request (new booking_id returned).
| Name | Type | Req | Description |
|---|---|---|---|
| accept_option_index | integer | – | Index into needs_input_options to accept |
| booking_id | string | yes | – |
| datetime | string | – | New requested time, ISO-8601; naive means the merchant's local wall time |
| party_size | integer | – | – |
| window_minutes | integer | – | – |
No output schema declared.
No examples provided.
place_booking Place a booking (async) ~503
Request a table reservation. Returns booking_id with state 'queued' immediately; fulfillment is asynchronous (a call is placed to the merchant). Poll get_booking_status or supply callback_url for webhooks. RETRY SAFETY: pass a unique client_reference_id (recommended: always); if this call times out or errors ambiguously, retry with the SAME client_reference_id and the registry returns the already-created booking instead of double-booking the restaurant. Never re-call place_booking after a timeout without one. If the merchant counter-offers a time within window_minutes and accept_within_window=true, it is auto-accepted (recommended). Otherwise the booking pauses in needs_input for you to resolve via modify_booking. Merchants on the human_call channel are fulfilled by a human operator during the operator window published in get_registry_meta — those bookings queue until worked (up to the channel SLA), so book ahead rather than for the next hour.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_within_window | boolean | – | Auto-accept merchant counter-offers inside the window (recommended: true) |
| callback_url | string | – | Webhook URL for booking state-change events |
| client_reference_id | string | – | Your unique ID for this booking request (a UUID is ideal). Retrying with the same value returns the existing booking (idempotent_replay: true) instead of creating a duplicate; the same value with dif… |
| contact | string | – | Optional phone/email for confirmation relay to the end human |
| datetime | string | yes | Requested time, ISO-8601. Naive ('2026-07-18T19:00') means the merchant's LOCAL wall time (see the merchant's timezone field); an explicit offset ('2026-07-18T19:00:00+09:00') is also accepted |
| merchant_id | string | yes | – |
| party_size | integer | yes | – |
| reservation_name | string | yes | Name for the reservation |
| sandbox_outcome | string | – | TEST ONLY, sandbox merchants (sandbox: true): force the simulated call's result so you can exercise a specific branch on demand — confirmed, no_answer (retries then fails), counter_offer (pauses in n… |
| special_requests | string | – | – |
| window_minutes | integer | – | Acceptable +/- window around datetime |
No output schema declared.
No examples provided.
search_merchants Search merchants ~426
Filter-based search over the restaurant registry (coverage cities + timezones in get_registry_meta). NOT ranked: results come back in deterministic order (merchant_id ASC by default; distance ASC when lat/lng given and order_by="distance"). Returns compact records with pagination. Use get_merchant for the full signal dump on a specific merchant. All filters are optional and combinable.
| Name | Type | Req | Description |
|---|---|---|---|
| attribute_tags | array | – | Match ALL of these attributes, e.g. ['outdoor_seating','vegetarian_friendly'] |
| bookable_only | boolean | – | Only merchants the registry can book right now (phone-verified, accepts reservations, not opted out) |
| cuisine_tags | array | – | Match ANY of these cuisines, e.g. ['japanese','korean'] |
| lat | number | – | Latitude for geo-radius filter (requires lng and radius_km) |
| limit | integer | – | – |
| lng | number | – | – |
| neighborhood | string | – | Exact neighborhood name, e.g. 'Mission' |
| offset | integer | – | – |
| open_at | string | – | ISO-8601 datetime; only merchants open at this time. With an explicit offset ('2026-07-18T19:00:00+09:00' or trailing Z) the instant is evaluated in each merchant's own timezone; without one it means… |
| order_by | string | – | – |
| party_size | integer | – | Only merchants that can seat this party size |
| price_band_max | integer | – | – |
| price_band_min | integer | – | – |
| radius_km | number | – | Radius in km around lat/lng |
| sandbox | boolean | – | Filter by merchant kind. true = sandbox test merchants only (safe integration targets: they book end-to-end and return a SIMULATED confirmation, never dialing a real venue). false = real merchants on… |
No output schema declared.
No examples provided.
submit_feedback Submit post-visit feedback ~136
Report how a confirmed reservation actually went. Accepted only against a confirmed booking_id, once per booking, within 14 days of confirmation. Structured fields first; optional free text ≤ 500 chars. This corpus is served raw to all agents via get_merchant — it is never editorialized or turned into a score.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | – |
| free_text | string | – | – |
| matched_description | boolean | – | Did the merchant match the registry's description? |
| reservation_honored | boolean | yes | Did the merchant honor the reservation? |
| seated_on_time | boolean | – | – |
| would_repeat | boolean | – | – |
No output schema declared.
No examples provided.
What is the Mercantry Registry MCP server?
Mercantry Registry is an MCP server listed in the public MCP registry as org.mercantry/registry. Agent-native registry: 168k+ real restaurants in LA, Hong Kong & Tokyo. Unranked, honest signals. This page covers its hosted endpoint (https://mercantry.org/mcp).
Is the Mercantry Registry MCP server safe to use?
Mercantry Registry scores 75 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 Mercantry Registry MCP server expose?
Mercantry Registry exposes 9 tools: search_merchants, get_merchant, get_availability, place_booking, get_booking_status, and 4 more. Their descriptions and schemas cost roughly 1,570 tokens of context every time the server is loaded.
Does the Mercantry Registry MCP server require authentication?
No. We connected to Mercantry Registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mercantry Registry MCP server still maintained?
Mercantry Registry is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.