Hosted MCP server/Search

DishDirectory.com MCP server

Hosted at dishdirectory.com·Streamable HTTP

DishDirectory publishes an MCP server over Streamable HTTP with 11 read-only tools for restaurant and dish search, places, categories, stats, sources, affiliate products, and academy courses. It needs no key and is limited to 300 requests per minute per client.

dishdirectory.com Streamable HTTP No authentication Source checked Nov 16, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Agents answering restaurant, dish, place, product, or course questions from DishDirectory data without a key.

  • Search published restaurants by text, place, or category.
  • Read one restaurant or affiliate product by slug.
  • List countries, cities, categories, sources, and academy courses.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds DishDirectory.com as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http dishdirectory-com https://dishdirectory.com/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://dishdirectory.com/mcp
Host
dishdirectory.com · /mcp
Transport
Streamable HTTP
Authentication
No authentication
Server name
dishdirectory-com
Listing type
Community or directory listing

The installer uses the server name dishdirectory-com. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that dishdirectory-com appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Search published restaurants by text, place, or category. Check the result before you give the server more access.

  3. 3
    Check permissions.

    The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.

Server responded when checked

We reached dishdirectory.com when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 16, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

DishDirectory.com documentationhttps://dishdirectory.com/developers