About Mercantry Registry
Mercantry Registry is an open commerce registry for AI agents, with structured restaurant data for Los Angeles, Hong Kong, and Tokyo. It supports merchant discovery and a sandbox booking flow; booking fulfillment for real merchants is not live.
Key features
- 01Restaurant discovery across three cities
- 02Merchant details with field provenance
- 03Availability and booking tools
- 04End-to-end sandbox booking flow
- 05Booking status, changes, and cancellation
Use cases
- 01Finding restaurants using documented filters
- 02Testing booking flows with fictional merchants
- 03Managing a sandbox booking through cancellation
MCP support
Exposes merchant search, details, availability, booking, feedback, and registry metadata tools over Streamable HTTP MCP. Real merchants are discovery-only; booking fulfillment is available only for sandbox merchants.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mercantry.org/mcpclaude mcp add --transport http org-mercantry-registry https://mercantry.org/mcp{"mcpServers":{"org-mercantry-registry":{"type":"http","url":"https://mercantry.org/mcp"}}}Open in Cursor{"servers":{"org-mercantry-registry":{"type":"http","url":"https://mercantry.org/mcp"}}}Open in VS Code{"mcpServers":{"org-mercantry-registry":{"type":"http","url":"https://mercantry.org/mcp"}}}{"mcpServers":{"org-mercantry-registry":{"serverUrl":"https://mercantry.org/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
9| Parameter | Type | Required | Description |
|---|---|---|---|
| lat | number | No | Latitude for geo-radius filter (requires lng and radius_km) |
| lng | number | No | |
| limit | integer | No | |
| offset | integer | No | |
| open_at | string | No | 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 each merchant's local wall clock |
| sandbox | boolean | No | 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 only — use this for any booking a human will act on. Omitted = both. Every result carries `sandbox`; never present a sandbox confirmation to a user as a real reservation. |
| order_by | enum | No | merchant_id | distance |
| radius_km | number | No | Radius in km around lat/lng |
| party_size | integer | No | Only merchants that can seat this party size |
| cuisine_tags | array | No | Match ANY of these cuisines, e.g. ['japanese','korean'] |
| neighborhood | string | No | Exact neighborhood name, e.g. 'Mission' |
| bookable_only | boolean | No | Only merchants the registry can book right now (phone-verified, accepts reservations, not opted out) |
| attribute_tags | array | No | Match ALL of these attributes, e.g. ['outdoor_seating','vegetarian_friendly'] |
| price_band_max | integer | No | |
| price_band_min | integer | No |
Details
From the project READMEMercantry
Mercantry is an open commerce registry for AI agents — structured merchant data, honest signals, and real-world booking fulfillment.
Current status — read this first. Mercantry is pre-launch. What is real and what is not, precisely:
- The merchant data is real: 168,000+ restaurants across Los Angeles, Hong Kong, and Tokyo, built exclusively from openly licensed sources (Overture Maps CDLA-P-2.0 + official government registers), conflated with per-field provenance and QA-gated versioned releases. Live counts:
get_registry_meta.- Real merchants are discovery-only for now:
place_bookingagainst a real merchant returns the structured rejectionfulfillment_not_live. A booking guard makes it structurally impossible for our booking simulator to dial a real restaurant.- The booking loop is testable end-to-end against
sandbox: truemerchants — fictional records with deterministic outcomes ("test cards for bookings"). Do not call sandbox phone numbers; they are not real businesses.- Fulfillment, when it launches, is human-operated phone booking on a phone-verified merchant tranche (voice automation is deferred). Outbound-calling sections of the spec operate only after legal review — publication of the spec is not operation.
- Mercantry is built and operated by a team of AI agents with human oversight, stated here as a fact rather than a gimmick.
Connect your agent
The live endpoint serves MCP over Streamable HTTP:
claude mcp add --transport http mercantry https://agentic-commerce-registry.fly.dev/mcp
- REST mirror:
/v1— self-describing via/v1/openapi.json - Discovery manifest:
/.well-known/mcp.json· agent card:/.well-known/agent-card.json· health:/healthz· PII-free ops stats:/v1/stats· privacy policy:/privacy· demo & reviewer guide:/demo - Keys are optional (abuse control, not gating):
POST /v1/keyswithdeveloper_name+contact. All reads are free and unauthenticated. - Bulk export encouraged:
GET /v1/export/merchants.ndjson— caching, embedding, and training on the data are permitted under the open license.
Copy-paste integrations — curl, Claude Code/Desktop, raw MCP JSON-RPC, OpenAI Agents SDK, LangChain, webhook receiver: examples/. Agent-first tool documentation with example transcripts: docs/mcp-tools.md. If you are an agent working in this repo, read AGENTS.md.
MCP tools
search_merchants (filter-based, never ranked, deterministic documented order) · get_merchant (full signal dump: every field, raw feedback history, operational stats, per-field provenance) · get_availability (honest: performed_at_booking) · place_booking (async) · get_booking_status · modify_booking · cancel_booking (mandatory when plans change — no-shows are tracked per developer key) · submit_feedback (confirmed bookings only, once, within 14 days) · get_registry_meta (evaluate the registry itself, staleness included)
Run it yourself
npm install
npm run dev # seeds a sandbox corpus on first boot; everything in one process
| Surface | Where |
|---|---|
| MCP (Streamable HTTP) | http://localhost:4100/mcp |
| REST mirror + OpenAPI | http://localhost:4100/v1 |
| Landing page (public fact page) | http://localhost:4100/ |
Ops Console (gate with OPS_TOKEN) | http://localhost:4100/ops/ |
| Booking status pages | http://localhost:4100/status/:booking_id |
npm test # full suite
npm run typecheck
Deployment (Docker/Fly.io), agent onboarding, and the security checklist: docs/deployment.md.
Architecture
┌─────────────┐ ┌──────────────┐ ┌────────────────────┐
│ Agent │────▶│ MCP Server │────▶│ Fulfillment │
│ (customer) │◀────│ src/mcp │◀────│ Orchestrator │
└─────────────┘ └──────┬───────┘ │ src/orchestrator │
│ │ └─ human operator │
┌──────▼───────┐ └─────────┬──────────┘
│ Registry DB │◀──────────────┘
│ src/db │ ┌────────────────────┐
└──────▲───────┘ │ Ops Console │
│ │ src/ops + src/api │
┌──────┴───────┐ └────────────────────┘
│ Ingestion │ src/ingest — LA · HK · Tokyo,
│ & QA gate │ openly licensed sources only
└──────────────┘
The customer is the agent, not the human. One uniform interface with swappable fulfillment backends: agents integrate once; behind the interface, fulfillment can graduate from human phone calls to native merchant integrations without the agent changing a line.
Hard rules encoded in this codebase
- No ranking, ever. No score fields exist in the schema; search order is deterministic and documented. The registry returns signals, never ordered opinions.
- No scraped review text. The only feedback served is transaction-verified, submitted by agents against confirmed bookings.
- Openly licensed data only. Overture Maps (CDLA-P-2.0) + official government registers; per-field provenance with timestamps; QA-gated releases with published drop counts.
- Opt-out is immediate and permanent. A merchant requesting removal is hard-excluded from discovery and booking the same day.
- Every booking is auditable. Full event log: tool calls, transcripts, timestamped state transitions.
- PII is minimal. Reservation name/contact stored only for the booking, never exposed via read tools.
- Honesty over polish.
get_availabilitysaysperformed_at_bookinginstead of pretending;get_registry_metaexposes our own staleness; sandbox vs. real is labeled per merchant.
Spec
The full product spec lives at docs/requirements.md. Sections describing outbound calling are published for openness but nothing in them operates until legal review is complete — see the banner at the top of that document.
License
Apache-2.0. The registry spec, code, and data schema are open — openness is the strategy, not a concession.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.