General Tools

yentaknows.ai

An MCP server for searching and retrieving published venues and travel destinations with filters for location, cuisine, price, reservations, proximity, and opening hours.

1 endpoint21 known toolsFirst detected September 10, 2026Last detected September 10, 2026

ENDPOINT 1

https://yentaknows.ai/mcp

No auth detected

MCP server metadata

Name: Yenta Directory
Version: 0.1.0

Capabilities

promptsresourcestools

Server instructions

Yenta directory: find published venues, cities and destinations and act on them BY NAME — no reconnect. Every result is partner-approved and versioned with a `source` freshness reference. search_venues / search_destinations find one; the venue_* / destination_* tools then read a named venue or destination directly (pass a slug if ambiguous). Live results also carry an `mcp_endpoint` (under venues.dev.yentaknows.ai); connect there only to transact, e.g. booking. Read-only; no auth. Powered by Yenta.

Known tools 21

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 given day/time, or open now) — all HARD filters that exclude on a miss, plus a HARD experiential-facet filter (facets, '<facet_type>:<value>' tokens from facet_vocabulary) — with prefer_cuisine, prefer_neighbourhood, avoid and prefer_facets as SOFT preferences that only rank a venue up or down and never drop it; each result carries the venue's capabilities and, when it is live, its mcp_endpoint.

Potential side effects

list_cities

List the cities that have at least one published venue.

Inferred read-only

get_venue

Get one published venue's summary, capabilities and live mcp_endpoint by its slug.

Inferred read-only

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_endpoint) is always returned, while include opts into heavier per-venue reads — hours, dietary (dietary-tag/allergen vocabulary), attributes (facets) and menu_summary — with items coming back in the requested order (a repeated slug resolves once) and not_found listing any requested slug that did not resolve to a published venue.

Inferred read-only

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.

Inferred read-only

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_venues or search_destinations for type-specific filters such as cuisine, hours or area.

Inferred read-only

get_destination

Get one published destination's summary and live mcp_endpoint by its slug.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

venue_profile

Get a named venue's published profile summary — give its name (and city) or slug.

Inferred read-only

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.

Inferred read-only

venue_dietary_options

List a named venue's declared dietary tags and allergens — the exact spellings venue_menu_search matches literally.

Inferred read-only

venue_faq

Search a named venue's published FAQs, optionally filtered by text.

Inferred read-only

venue_links

Get a named venue's published booking and other links (connect to its mcp_endpoint to actually book).

Inferred read-only

destination_overview

Get a named destination's summary: counts by category, currency, timezone.

Inferred read-only

destination_facets

List a named destination's valid area, category and tag filter values.

Inferred read-only

destination_listings

Search a named destination's listings by text, category, area and tags (slugs from destination_facets); optionally near another listing.

Inferred read-only

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.

Inferred read-only

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).

Inferred read-only

destination_guide

Read a named destination's editorial guides such as weather, getting here and safety.

Inferred read-only

destination_faq

Search a named destination's FAQs, optionally filtered by text.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.yenta-directory]
url = "https://yentaknows.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "yenta-directory": {
      "type": "http",
      "url": "https://yentaknows.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: yenta-directory
Remote MCP URL: https://yentaknows.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "yenta-directory": {
      "url": "https://yentaknows.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "yenta-directory": {
      "type": "http",
      "url": "https://yentaknows.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "yenta-directory",
  "transport": "streamable-http",
  "url": "https://yentaknows.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.