Yenta Directory is an MCP server with 21 tools an agent can call, among them destination_events, destination_facets, destination_faq. It answers at https://mcp.yentaknows.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Restaurants and bars in 10 cities: hours, menus, dietary tags, events and booking; destinations.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
destination_events | Find a named destination's events overlapping a date window (default from today; a recurring event's span is not a single date — read its recurrence). Inputs: destination, from_date, to_date, category, area, limit |
destination_facets | List a named destination's valid area, category and tag filter values. Inputs: destination, kind |
destination_faq | Search a named destination's FAQs, optionally filtered by text. Inputs: destination, query, limit, cursor |
destination_guide | Read a named destination's editorial guides such as weather, getting here and safety. Inputs: destination, topic, query |
destination_listing | Get one listing's full detail by its id, including a live linked venue's mcp_endpoint and linked_venue_slug to read or book it via the venue_* tools. Inputs: destination, listing_id |
destination_listings | Search a named destination's listings by text, category, area and tags (slugs from destination_facets); optionally near another listing. Inputs: destination, query, category, area, tags, language |
destination_overview | Get a named destination's summary: counts by category, currency, timezone. Inputs: destination |
facet_vocabulary | The closed facet vocabulary (vibe, cuisine, dietary, and more) plus today's live cuisine, price_band and neighbourhood values across published venues, the exact values search_venues' matching filters accept. |
get_destination | Get one published destination's summary and live mcp_endpoint by its slug. Inputs: destination_slug |
get_venue | Get one published venue's summary, capabilities and live mcp_endpoint by its slug. Inputs: venue_slug |
get_venues | Get several published venues' summaries in ONE call by their slugs — the batch counterpart to get_venue, so a shortlist from search_venues needs no per-slug round-trip; the base view (identity, essentials, capabilities, booking, mcp_endpoin Inputs: slugs, include |
list_cities | List the cities that have at least one published venue. Inputs: limit, cursor |
search | Search published venues and destinations together in one call, each result tagged with its kind (venue or destination); pass kind to scope to one type, query to match names and venue descriptions, and city to narrow venues, then use search_ Inputs: query, city, kind, limit, cursor |
search_destinations | Search published travel destinations by name; omit the query to list all, and connect to each result's mcp_endpoint for its listings, events and guides. Inputs: query, limit, cursor |
search_menus | Search menu items across all published venues by text, city, required dietary tags and allergens to avoid, each result tagged with its venue so an agent can rank venues in one call. Inputs: query, city, dietary_tags, allergens, limit, cursor |
search_venues | Search published venues by name or description, optionally filtered by city, cuisine, price band, neighbourhood, whether the venue takes reservations, proximity (near a lat/long within a radius, nearest first) and opening hours (open on a g Inputs: query, city, cuisine, price_band, neighbourhood, accepts_reservations |
venue_dietary_options | List a named venue's declared dietary tags and allergens — the exact spellings venue_menu_search matches literally. Inputs: venue, city |
venue_faq | Search a named venue's published FAQs, optionally filtered by text. Inputs: venue, city, query, limit, cursor |
venue_links | Get a named venue's published booking and other links (connect to its mcp_endpoint to actually book). Inputs: venue, city |
venue_menu_search | Search a named venue's menu by text, required dietary tags and allergens to avoid; call venue_dietary_options first for the exact spellings. Inputs: venue, city, query, dietary_tags, allergens, limit |
venue_profile | Get a named venue's published profile summary — give its name (and city) or slug. Inputs: venue, city |
Every block below points at https://mcp.yentaknows.ai/mcp. Pick your client and copy.
claude mcp add --transport http yenta-directory https://mcp.yentaknows.ai/mcp
{
"mcpServers": {
"yenta-directory": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.yentaknows.ai/mcp"]
}
}
}{
"mcpServers": {
"yenta-directory": {
"url": "https://mcp.yentaknows.ai/mcp"
}
}
}{
"servers": {
"yenta-directory": {
"type": "http",
"url": "https://mcp.yentaknows.ai/mcp"
}
}
}{
"context_servers": {
"yenta-directory": {
"url": "https://mcp.yentaknows.ai/mcp"
}
}
}{
"mcpServers": {
"yenta-directory": {
"serverUrl": "https://mcp.yentaknows.ai/mcp"
}
}
}{
"mcpServers": {
"yenta-directory": {
"url": "https://mcp.yentaknows.ai/mcp"
}
}
}name: Yenta Directory
version: 0.0.1
schema: v1
mcpServers:
- name: Yenta Directory
type: streamable-http
url: https://mcp.yentaknows.ai/mcp{
"mcpServers": {
"yenta-directory": {
"httpUrl": "https://mcp.yentaknows.ai/mcp"
}
}
}{
"mcpServers": {
"yenta-directory": {
"type": "http",
"url": "https://mcp.yentaknows.ai/mcp"
}
}
}{
"mcpServers": {
"yenta-directory": {
"url": "https://mcp.yentaknows.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.yentaknows.ai%2Fmcp&type=streamable_http&id=yenta-directory&name=Yenta%20Directory
It answered our last check on 19 October 2026 in 918 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by yentaknows.ai and served from mcp.yentaknows.ai, the vendor's own domain: https://mcp.yentaknows.ai/mcp.
21, as returned by the server's own tools/list on 10 September 2026: destination_events, destination_facets, destination_faq, destination_guide, destination_listing, destination_listings, destination_overview, facet_vocabulary, and 13 more.
It answered our last check on 19 October 2026 in 918 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.yentaknows.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.yentaknows. Endpoint host: mcp.yentaknows.ai. ARD identifier: urn:air:ai.yentaknows:mcp:directory.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.