# Yenta Directory

> Anonymous, read-only cross-venue discovery of partner-approved venues, cities, destinations.

- name: ai.yentaknows/directory
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 93/100
- quality: 84/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/ai.yentaknows%2Fdirectory
- tools: https://api.protogrid.dev/v1/servers/ai.yentaknows%2Fdirectory/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% ~updated-40d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 84/100 (good)

### protocol: 100 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- pass `protocol.list_ttl`: tool list is cacheable (ttlMs 60000)

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 16 of 16 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 5,002 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 26 tool changes in 30 days
- fail `stability.rug_pull`: 10 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 16, about 5,002 tokens to load them all
- tool set hash: abdb6cef8483f350cf9d95298b767cdd
- tools last changed: 2026-10-07T09:22:21.955Z
- badge: [![protogrid quality](https://protogrid.dev/badge/ai.yentaknows/directory.svg)](https://protogrid.dev/servers/ai.yentaknows/directory)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-07 `destination_facets` removed
  - List a named destination's valid area, category and tag filter values (the destination's own host calls this list_facets).
- 2026-10-07 `venue_links` removed
  - 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).
- 2026-10-07 `search_destinations` removed
  - 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.
- 2026-10-07 `destination_listing` removed
  - 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).
- 2026-10-07 `venue_dietary_options` removed
  - 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).
- 2026-10-07 `venue_menu_search` removed
  - 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).
- 2026-10-07 `facet_vocabulary` removed
  - 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.
- 2026-10-07 `get_destination` removed
  - 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.
- 2026-10-07 `get_venues` removed
  - 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.
- 2026-10-07 `get_venue` removed
  - 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.

Full history: https://api.protogrid.dev/v1/servers/ai.yentaknows%2Fdirectory/changes

## Remotes

- https://yentaknows.ai/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (16)

- `destination_events`: Find what is on in a named destination: events from today onwards. A recurring event's dates are its series span, so read its recurrence. Offer booking_url when present; cite canonical_url, the destination's page.
- `destination_faq`: Answer a question about a named destination from its published FAQs; omit query to read them all.
- `destination_guide`: Read a named destination's travel guides: weather, getting here, transport, entry requirements, safety and more. Pass topic (from destination_overview guide_topics) to read one subject; page with cursor.
- `destination_listings`: Find places to stay, eat and visit in a named destination by text, category, area or tags. Every query word matches, in any order; each business appears once (also_listed_as) with a snippet and map_url, so call it again with listing_id for the full text. An unknown filter value's reason lists the valid ones.
- `destination_offers`: Find a named destination's current deals and packages, with the partner booking link. Only offers valid on valid_on (today by default) are returned. Offer booking_url when present; cite canonical_url, the destination's page.
- `destination_overview`: One call answers what a destination offers and what's on: counts, a few places, next events and guide topics. It counts offers, seasonality and FAQs too, and names the categories and areas listings, events and offers filter by. Drill in with destination_listings / destination_events only if preview.complete is false.
- `destination_seasonality`: Get a named destination's best time to visit, weather and wildlife seasons (e.g. whale watching), month by month.
- `fetch`: Read the full page for one search result id as Markdown text, with its citable url. Ids look like "venue:acme-bistro", "destination:los-cabos" or "listing:los-cabos:1234".
- `list_cities`: List the cities that have published restaurants and bars. Travel destinations such as Los Cabos are not cities here; read one with destination_overview.
- `search`: Search venues, travel destinations and places inside destinations by name or keyword. Returns results of id, title and url; pass an id to fetch for the full page. For filters use search_venues, search_menus or destination_listings.
- `search_menus`: Find dishes across all venues by text, city, dietary tags or allergens to avoid. Each item is tagged with its venue, so one call compares venues; for one named venue use venue_menu.
- `search_venues`: Find restaurants and bars by city, cuisine, opening time or features. Filters are HARD, prefer_* and avoid are SOFT (rank only), and query is ONE keyword. Each result has slug, capabilities, open_now and distance_km; a place inside a destination is not here, use destination_listings.
- `venue_events`: Find what is on at a named venue: dated events from its local today onwards. Filter by exact event_type if you know it. If not available, check the capabilities venue_profile lists; the venue may not publish this.
- `venue_faq`: Answer a question about a named venue from its published FAQs; omit query to read them all. If not available, check the capabilities venue_profile lists; the venue may not publish this.
- `venue_menu`: Find dishes at a named venue, e.g. venue="Acme Bistro", dietary_tags=["vegan"], allergens=["milk"]. Filter by text, tags, allergens or max_price; unfiltered, item lists its dietary tags, example dishes and allergen counts. If not available, check the capabilities venue_profile lists; the venue may not publish this.
- `venue_profile`: Get a venue's hours, address, map, phone, booking and links by name or slug, e.g. venue="Acme Bistro". It also holds cuisine, attributes, menu_summary and capabilities (the other venue_* tools that answer for it); hours_summary is ready to quote.