3 minTime to key
NoNo-human path
3Human gates
5/10Onboarding score
Manual reviewPartner applicationPhone OTP
Fastest path to a key
- No developer API key (public API shut down). Personal agent path: add remote MCP https://mcp-server.zomato.com/mcp in Claude (custom connector or official directory listing), ChatGPT, VS Code or Postman.
- Phone OTPClient registers via DCR (/register) -> OAuth authorize -> log in to Zomato (phone OTP) -> token.
- Tools: restaurant discovery, menus, cart, place order, QR-code payment (user pays via UPI QR).
- Manual reviewCustom clients (e.g. Claude Code localhost redirect) are NOT on the redirect-URI allowlist -> must fill 'MCP Developer Access' form (personal use only) and wait for review.
- Working API key
Biggest gap
No third-party apps permitted; redirect allowlist breaks DCR for new clients; robots.txt contradicts the llms.txt invitation.
Worth copying
llms.txt written as an operating manual for browser agents with explicit confirm-before-order rule; DCR-enabled remote MCP with one-click VS Code install.
Sources (10) · checked 2026-10-11
- https://github.com/Zomato/mcp-server-manifest
- https://raw.githubusercontent.com/Zomato/mcp-server-manifest/master/README.md
- https://mcp-server.zomato.com/mcp (probed: 401)
- https://mcp-server.zomato.com/.well-known/oauth-protected-resource
- https://mcp-server.zomato.com/.well-known/oauth-authorization-server
- https://www.zomato.com/llms.txt
- https://www.zomato.com/robots.txt
- https://www.zomato.com/mcp-tools.md (403)
- https://claude.com/marketplace/connectors/zomato
- https://www.analyticsvidhya.com/blog/2025/11/zomato-mcp-server/
11Readiness score / 100
L0 Agent-invisibleBeats 3% of 1,846 companies
Access10/20
Context1/20
Interfaces0/32
Onboarding0/19
Trust0/9
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +10 Agents get the real page, not a bot wall. Serve the homepage to AI user-agents (Claude-User, ChatGPT-User) without a challenge or 403.
- +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
All 20 checks
- FAILAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- FAILllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- FAILSitemap2
- PASSStructured metadata1
- FAILPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- FAILSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- FAILFree tier or test mode3
- FAILAgent manifests4
- FAILsecurity.txt2
- FAILPublic status page3
Your fix pack: 18 changes, up to +89 points
Each change is ready to paste, filled in for zomato.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/zomato.com)