# Yenta Directory (remote · yentaknows.ai) Anonymous, read-only cross-venue discovery of partner-approved venues, cities, destinations. - Trust score: 80/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-25 ## Components - remote · `yentaknows.ai`: 80/100 (this document), [markdown](https://verifymcp.io/servers/ai-yentaknows-directory/yentaknows.md), [page](https://verifymcp.io/servers/ai-yentaknows-directory/yentaknows) ## Channel facts - Endpoint: `https://yentaknows.ai/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.1.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-25. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 83/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 3036 tokens (~144/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 50/100 - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the Yenta Directory MCP server? Yenta Directory is a hosted endpoint at https://yentaknows.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http ai-yentaknows-directory 'https://yentaknows.ai/mcp' ``` ### Cursor ```json { "mcpServers": { "ai-yentaknows-directory": { "url": "https://yentaknows.ai/mcp" } } } ``` ### VS Code ```json { "servers": { "ai-yentaknows-directory": { "type": "http", "url": "https://yentaknows.ai/mcp" } } } ``` ### Codex ```toml [mcp_servers.ai-yentaknows-directory] url = "https://yentaknows.ai/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "ai-yentaknows-directory": { "type": "remote", "url": "https://yentaknows.ai/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add ai-yentaknows-directory --url 'https://yentaknows.ai/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: ai-yentaknows-directory: url: "https://yentaknows.ai/mcp" ``` ### Netclaw ```json { "McpServers": { "ai-yentaknows-directory": { "Transport": "http", "Url": "https://yentaknows.ai/mcp" } } } ``` ### Vellum ```bash assistant mcp add ai-yentaknows-directory -t streamable-http -u 'https://yentaknows.ai/mcp' ``` ### Other ```json { "mcpServers": { "ai-yentaknows-directory": { "type": "http", "url": "https://yentaknows.ai/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-25 (score 80, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-09-24 (score 79, 0) - [security] Tool “venue_menu_search” rewrote its description, which is the text the model reads - [security] Tool “destination_events” rewrote its description, which is the text the model reads - [security] Tool “destination_facets” rewrote its description, which is the text the model reads - [security] Tool “destination_faq” rewrote its description, which is the text the model reads - [security] Tool “destination_guide” rewrote its description, which is the text the model reads - [security] Tool “destination_listing” rewrote its description, which is the text the model reads - [security] Tool “destination_listings” rewrote its description, which is the text the model reads - [security] Tool “destination_overview” rewrote its description, which is the text the model reads - [security] Tool “facet_vocabulary” rewrote its description, which is the text the model reads - [security] Tool “get_destination” rewrote its description, which is the text the model reads - [security] Tool “get_venue” rewrote its description, which is the text the model reads - [security] Tool “venue_dietary_options” rewrote its description, which is the text the model reads - [security] Tool “venue_faq” rewrote its description, which is the text the model reads - [security] Tool “venue_links” rewrote its description, which is the text the model reads - [security] Tool “venue_profile” rewrote its description, which is the text the model reads - [cosmetic] “destination_listings” reworded the description of “radius_km” ### 2026-09-23 (score 79, +1) No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-21 (score 78, +1) No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-18 (score 77, +1) No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-16 (score 76, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-14 (score 75, +1) No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-12 (score 74, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (21) ### `search_venues` (~659 tokens) 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, ':' 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. Input parameters: - `accepts_reservations`: Filter by whether the venue takes reservations (has a live booking tool or a booking link); omit for both. - `at`: A 24-hour HH:MM time; with open_on, require the venue be open then. - `avoid` (array): Soft preference: venues matching these cuisine/neighbourhood tokens rank LOWER; not dropped. - `city`: Only return venues in this city (case-insensitive); call list_cities for the exact values this directory knows. - `cuisine`: Only return venues with this cuisine (case-insensitive exact match). - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `facets` (array): HARD experiential-facet filter: each token is ':' (e.g. 'dietary:vegetarian', 'vibe:romantic'). A venue must match every facet_type given (values OR within a type, types AND across… - `limit` (integer): Maximum number of items to return. - `near`: Only return venues within radius_km of this 'latitude,longitude' point, nearest first, each with a distance_km; venues with no coordinates are excluded. - `neighbourhood`: Only return venues in this neighbourhood (case-insensitive exact match). - `open_now`: Only return venues open (true) or closed (false) at their own local time now; venues with no timezone or hours are excluded. - `open_on`: Only return venues open on this weekday (optionally at 'at'); venues with no published hours are excluded. - `prefer_cuisine` (array): Soft preference: venues of these cuisines rank higher; non-matches are NOT dropped. - `prefer_facets` (array): SOFT experiential-facet preference, same ':' tokens as facets: a venue that declares them ranks higher but is NEVER dropped. Call facet_vocabulary for the legal types and values. - `prefer_neighbourhood` (array): Soft preference: venues in these neighbourhoods rank higher; non-matches are NOT dropped. - `price_band`: Only return venues in this price band, e.g. '$$' (case-insensitive). - `query`: Text to match against venue names and descriptions; omit to list all. - `radius_km`: Search radius in km around 'near' (default applied when omitted). Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `list_cities` (~55 tokens) List cities List the cities that have at least one published venue. Input parameters: - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `limit` (integer): Maximum number of items to return. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `get_venue` (~65 tokens) Get venue Get one published venue's summary, capabilities and live mcp_endpoint by its slug — always available for any published venue, so use this if venue_profile reports the venue is not available. Input parameters: - `venue_slug` (string, required): The venue's slug, as returned by search_venues. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `get_venues` (~221 tokens) Get venues (batch) 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. Input parameters: - `include` (array): Optional add-ons, any of: attributes, dietary, hours, menu_summary. Omit for the lean base view; an unknown value is a 422. - `slugs` (array, required): The venues' slugs, as returned by search_venues; duplicates resolve once. Either one slug per list entry, or comma-separated within an entry (a,b) — both work and mix; the cap applies to the total sl… Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `search_destinations` (~91 tokens) 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. Input parameters: - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `limit` (integer): Maximum number of items to return. - `query`: Text to match against destination names; omit to list all. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `search` (~180 tokens) Search venues and destinations 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. Input parameters: - `city`: Narrow VENUES to this city (case-insensitive); destinations have no city and are not narrowed by it. Call list_cities for the exact values. - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `kind`: Scope to 'venue' or 'destination'; omit to return both, each tagged kind. - `limit` (integer): Maximum number of items to return. - `query`: Match venue names/descriptions and destination names; omit for all. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `get_destination` (~62 tokens) Get destination Get one published destination's summary and live mcp_endpoint by its slug — always available for any published destination, so use this if destination_overview reports it is not available. Input parameters: - `destination_slug` (string, required): The destination's slug, as returned by search_destinations. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `search_menus` (~162 tokens) Search menus across venues 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. Input parameters: - `allergens` (array): Exclude items that declare any of these allergens (spelling-insensitive). - `city`: Only return items from venues in this city (case-insensitive); call list_cities for the exact values. - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `dietary_tags` (array): Require ALL of these dietary tags (case- and separator-insensitive). - `limit` (integer): Maximum number of items to return. - `query`: Text to match against menu item names and descriptions. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `facet_vocabulary` (~66 tokens) Facet vocabulary The closed VENUE 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 — for a destination's areas, categories and tags call destination_facets instead. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `venue_profile` (~112 tokens) Venue profile by name Get a named venue's published profile summary — give its name (and city) or slug; not every venue enables this richer profile, so if it reports the venue is not available, fall back to get_venue with the slug from search_venues (the venue's own host calls this get_venue_profile). Input parameters: - `city`: Disambiguate a name by city (call list_cities); ignored for a slug. - `venue` (string, required): Venue name or slug; call search_venues to discover one. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `venue_menu_search` (~178 tokens) Search a venue's menu by name Search a named venue's menu by text, required dietary tags and allergens to avoid; call venue_dietary_options first for the exact spellings (the venue's own host calls this search_menu). Input parameters: - `allergens` (array): Exclude items declaring any of these allergens (exact spelling). - `city`: Disambiguate a name by city (call list_cities); ignored for a slug. - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `dietary_tags` (array): Require ALL of these tags (exact spelling from venue_dietary_options). - `limit` (integer): Maximum number of items to return. - `query`: Text to match against item names and descriptions. - `venue` (string, required): Venue name or slug; call search_venues to discover one. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `venue_dietary_options` (~86 tokens) Venue dietary options by name List a named venue's declared dietary tags and allergens — the exact spellings venue_menu_search matches literally (the venue's own host calls this get_dietary_options). Input parameters: - `city`: Disambiguate a name by city (call list_cities); ignored for a slug. - `venue` (string, required): Venue name or slug; call search_venues to discover one. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `venue_faq` (~123 tokens) Venue FAQ by name Search a named venue's published FAQs, optionally filtered by text (the venue's own host calls this get_venue_faq). Input parameters: - `city`: Disambiguate a name by city (call list_cities); ignored for a slug. - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `limit` (integer): Maximum number of items to return. - `query`: Text to match against questions and answers. - `venue` (string, required): Venue name or slug; call search_venues to discover one. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `venue_links` (~82 tokens) Venue links by name Get a named venue's published booking and other links (connect to its mcp_endpoint to actually book; the venue's own host calls this get_venue_links). Input parameters: - `city`: Disambiguate a name by city (call list_cities); ignored for a slug. - `venue` (string, required): Venue name or slug; call search_venues to discover one. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `destination_overview` (~76 tokens) Destination overview by name Get a named destination's summary: counts by category, currency, timezone — if it reports the destination is not available, fall back to get_destination with the slug from search_destinations (the destination's own host calls this get_overview). Input parameters: - `destination` (string, required): Destination name or slug; call search_destinations to discover one. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `destination_facets` (~68 tokens) Destination facets by name List a named destination's valid area, category and tag filter values (the destination's own host calls this list_facets). Input parameters: - `destination` (string, required): Destination name or slug; call search_destinations to discover one. - `kind`: Return only this facet family; omit for all three. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `destination_listings` (~220 tokens) Search a destination's listings by name Search a named destination's listings by text, category, area and tags (slugs from destination_facets); optionally near another listing, and the destination's own host calls this search_listings. Input parameters: - `area`: Area slug from destination_facets. - `category`: Category slug from destination_facets. - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `destination` (string, required): Destination name or slug; call search_destinations to discover one. - `language`: Language code (e.g. 'en', 'es'); defaults to the destination's. - `limit` (integer): Maximum number of items to return. - `near_listing_id`: A listing id; returns listings within radius_km, nearest first. - `query`: Text to match listing names/descriptions. - `radius_km`: Search radius in km around near_listing_id; a larger value is reduced to the server maximum. - `tags` (array): Tag slugs; only listings carrying ALL are returned. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `destination_listing` (~91 tokens) Get a destination listing by name 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 (the destination's own host calls this get_listing). Input parameters: - `destination` (string, required): Destination name or slug; call search_destinations to discover one. - `listing_id` (string, required): The listing's id, as returned by destination_listings. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `destination_events` (~149 tokens) Search a destination's events by name 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; the destination's own host calls this search_events). Input parameters: - `area`: Area slug from destination_facets. - `category`: Category slug from destination_facets. - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `destination` (string, required): Destination name or slug; call search_destinations to discover one. - `from_date`: ISO date; defaults to today. - `limit` (integer): Maximum number of items to return. - `to_date`: ISO date; open-ended if omitted. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `destination_guide` (~78 tokens) Destination guides by name Read a named destination's editorial guides such as weather, getting here and safety (the destination's own host calls this get_guide). Input parameters: - `destination` (string, required): Destination name or slug; call search_destinations to discover one. - `query`: Text to match in guide title/body. - `topic`: Guide topic; omit for all. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ### `destination_faq` (~98 tokens) Destination FAQ by name Search a named destination's FAQs, optionally filtered by text (the destination's own host calls this get_faq). Input parameters: - `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page. - `destination` (string, required): Destination name or slug; call search_destinations to discover one. - `limit` (integer): Maximum number of items to return. - `query`: Text to match in question/answer. Output parameters: - `item` - `items` - `pagination` - `reason` - `sample` - `source` (object): FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:`` for every read that answers from one venue, and the literal ``directory`` for… - `status` (string) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-yentaknows-directory/yentaknows#diagnostics ## Score history - 2026-09-25: 80 - 2026-09-24: 79 - 2026-09-23: 79 - 2026-09-22: 78 - 2026-09-21: 78 - 2026-09-20: 77 - 2026-09-19: 77 - 2026-09-18: 77 - 2026-09-17: 76 - 2026-09-16: 76 - 2026-09-15: 75 - 2026-09-14: 75 - 2026-09-13: 74 - 2026-09-12: 74 - 2026-09-11: 73 - 2026-09-10: 73 ## Common questions ### What is the Yenta Directory MCP server? Yenta Directory is an MCP server listed in the public MCP registry as ai.yentaknows/directory. Anonymous, read-only cross-venue discovery of partner-approved venues, cities, destinations. This page covers its hosted endpoint (https://yentaknows.ai/mcp). ### Is the Yenta Directory MCP server safe to use? Yenta Directory scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Yenta Directory MCP server expose? Yenta Directory exposes 21 tools: search_venues, list_cities, get_venue, get_venues, search_destinations, and 16 more. Their descriptions and schemas cost roughly 2,922 tokens of context every time the server is loaded. ### Does the Yenta Directory MCP server require authentication? No. We connected to Yenta Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the Yenta Directory MCP server still maintained? Yenta Directory is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://yentaknows.ai/mcp - Repository: https://github.com/yenta-ai/yenta-mcp - Website: https://yentaknows.ai/ - Changelog RSS feed: https://verifymcp.io/servers/ai-yentaknows-directory/yentaknows.xml - Changelog JSON feed: https://verifymcp.io/servers/ai-yentaknows-directory/yentaknows.json - HTML version of this page: https://verifymcp.io/servers/ai-yentaknows-directory/yentaknows