# Mercantry Registry Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Mercantry Registry

Search and book restaurants in LA, Hong Kong and Tokyo with honest merchant data and real feedback.

- Record: https://musedirectory.ai/connector/mercantry-registry
- Category: Travel
- Developer: Mercantry (https://mercantry.org)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 890ms, checked 2026-09-28T07:16:07Z
- Endpoint: https://mercantry.org/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T05:15:47Z)
- Source: Found in the official MCP Registry (org.mercantry/registry) https://registry.modelcontextprotocol.io/v0/servers?search=org.mercantry%2Fregistry

Access 168,000+ verified restaurants across Los Angeles, Hong Kong, and Tokyo. Search by neighborhood, cuisine, price, availability and party size. Make phone-verified reservations with real-time booking status and post-visit feedback tracking.

Example request: "Find a Japanese restaurant with outdoor seating in the Mission district that can seat 4 people tonight at 7pm and book a table."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Mercantry Registry to help me. It is a free service with an MCP server at https://mercantry.org/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- search_merchants: 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
- get_merchant: 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.
- get_availability: 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.
- place_booking: 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 
- get_booking_status: 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 | 
- modify_booking: 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
- cancel_booking: 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.
- submit_feedback: 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 editor
- get_registry_meta: 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.

Screening checks:
- MCP handshake: pass (Answered in 274ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mercantry.org not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (9 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)