Yenta MCP server

• Registry nameai.yentaknows/directoryverified in the MCP registry

The registry name sits under yentaknows.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools17
• Server calls itselfYenta Directory
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 150 ms.

• Its tools do every use case we checked: look up a restaurant's approved menu and dietary options; check venue hours and upcoming events.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer462 ms
• Space in an agent's context≈ 5,210 tokensthe definitions of all its tools (17), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results17 of 17 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

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

• fetch

  Read a search result's full page: a restaurant's menu, dietary options, hours and events, or a destination's. Returns Markdown text with its citable url. Ids look like "venue:acme-bistro", "destination:los-cabos" or…

• 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…

• 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_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.

• send_feedback

  Send Yenta a report: data that is missing or looks wrong, a tool that was hard to use, or anything else. Stored for Yenta's team and never shown publicly; the answer carries a reference. Leave out personal details.

• 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…

• 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…

• 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_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.

• 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…

• 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…

• 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. Results carry booking_url, the partner's booking page when present, and canonical_url, the…

• 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_faq

  Answer a question about a named destination from its published FAQs; omit query to read them all.

• 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. Results carry booking_url, the partner's booking page when present, and canonical_url…

• destination_seasonality

  Get a named destination's best time to visit, weather and wildlife seasons (e.g. whale watching), month by month.