INDIVIDUAL MCP TOOL

destination_guide

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

yentaknows.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://yentaknows.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for destination_guide and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

yentaknows.ai

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.

Related tools

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.
list_cities — List the cities that have at least one published venue.
get_venue — Get one published venue's summary, capabilities and live mcp_endpoint by its 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_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.
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.
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.
get_destination — Get one published destination's summary and live mcp_endpoint by its slug.
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.