Skip to content

Mercantry Registry MCP server

org.mercantry/registrymercantry.orgstreamable-httpv0.1.0Scanned

Agent-native registry: 168k+ real restaurants in LA, Hong Kong & Tokyo. Unranked, honest signals.

9 tools: 1 can delete or cancel things, 4 change things and 4 only read.

Tools: 1 delete, 0 irreversible, 4 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Mercantry Registry MCP server can do

The Mercantry Registry MCP server is published by mercantry.org, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: cancel_booking) and create or change data (4 tools: place_booking, modify_booking, submit_feedback and get_registry_meta). 4 tools only read.

1 tool reads private data (get_availability); 1 tool can send data out of your system (place_booking).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • cancel_bookingCancel a booking in any non-terminal state, or a confirmed reservation (the registry notifies the merchant).No findings

    Why it is in this group

    • The name "cancel_booking" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    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.
Changes things 4Claude Code: ask
  • get_registry_metaEvaluate the registry itself: per-city coverage (with each city's IANA timezone), merchant/bookable counts, verification and freshness stats, feedback corpus size, schema version, …No findings

    Why it is in this group

    • The name "get_registry_meta" says "get": a word for reading.
    • The description's first verb is "evaluate": a word for a change.
    Description, as the server wrote it
    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.
  • modify_bookingAmend a booking before or after the call.No findings

    Why it is in this group

    • The name "modify_booking" says "modify": a word for a change.
    Description, as the server wrote it
    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).
  • place_bookingRequest a table reservation.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "request": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • submit_feedbackReport how a confirmed reservation actually went.No findings

    Why it is in this group

    • The name "submit_feedback" says "submit": a word for a change.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • get_availabilityV1 does NOT hold live table availability — availability is checked on the phone call at booking time.Reads private dataNo findings

    Why it is in this group

    • The name "get_availability" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "table": it reads databases.
    Description, as the server wrote it
    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.
  • get_booking_statusState machine position for a booking: pending → queued → in_progress → confirmed | failed | needs_input (plus cancelled).No findings

    Why it is in this group

    • The name "get_booking_status" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_merchantEvery field the registry holds on one merchant: schema fields, structured hours, raw feedback history, platform-observed operational stats, and per-field provenance with timestamps…No findings

    Why it is in this group

    • The name "get_merchant" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • search_merchantsFilter-based search over the restaurant registry (coverage cities + timezones in get_registry_meta).No findings

    Why it is in this group

    • The name "search_merchants" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mercantry.org/mcp: tools/list returned 9 tools to an anonymous client, including cancel_booking (destructive), place_booking (write), modify_booking (write), submit_feedback (write), get_registry_meta (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http registry https://mercantry.org/mcp
claude mcp add --transport http registry https://mercantry.org/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__registry__search_merchants",
      "mcp__registry__get_merchant",
      "mcp__registry__get_availability",
      "mcp__registry__get_booking_status"
    ],
    "ask": [
      "mcp__registry__place_booking",
      "mcp__registry__modify_booking",
      "mcp__registry__submit_feedback",
      "mcp__registry__get_registry_meta"
    ],
    "deny": [
      "mcp__registry__cancel_booking"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as registry. Review it before you use it.

Capability tags behind 2 rules
  • mcp__registry__get_availability private-data
  • mcp__registry__place_booking outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.mercantry/registry/verify?hash=14fc94bae48ae3620f9e18d8fe84e11b88e5da23a064845e9a00c0331805d241" | jq -e '.changed == false'

Pinned hash 14fc94bae48a, from Nov 18, 2026, 03:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.mercantry/registry/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.mercantry/registry
[![Anlyon Radar](https://radar.anlyon.com/badge/org.mercantry/registry.svg)](https://radar.anlyon.com/servers/org.mercantry/registry)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

Mercantry Registry MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mercantry Registry MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mercantry Registry MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_booking.

Can the Mercantry Registry MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Mercantry Registry MCP server have?

9 tools: 1 destructive, 4 write, 4 read. cancel_booking, place_booking, modify_booking, submit_feedback, get_registry_meta, search_merchants, get_merchant, get_availability and 1 more.

Does the Mercantry Registry MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mercantry Registry MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): place_booking.

Has the Mercantry Registry MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.