# Yenta Directory (remote · mcp.yentaknows.ai)

Restaurants and bars in 10 cities: hours, menus, dietary tags, events and booking; destinations.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.yentaknows.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-yentaknows-directory/mcp.md), [page](https://verifymcp.io/servers/ai-yentaknows-directory/mcp)

## Channel facts

- Endpoint: `https://mcp.yentaknows.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-11-05.

- **Endpoint Security**: 80/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 76/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 3906 tokens (~229/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 18 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://mcp.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://mcp.yentaknows.ai/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.ai-yentaknows-directory]
url = "https://mcp.yentaknows.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-yentaknows-directory": {
      "type": "remote",
      "url": "https://mcp.yentaknows.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-yentaknows-directory --url 'https://mcp.yentaknows.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-yentaknows-directory:
    url: "https://mcp.yentaknows.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-yentaknows-directory": {
      "Transport": "http",
      "Url": "https://mcp.yentaknows.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-yentaknows-directory -t streamable-http -u 'https://mcp.yentaknows.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-yentaknows-directory": {
      "type": "http",
      "url": "https://mcp.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-11-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 76, 0)

- [security] Tool “destination_offers” rewrote its description, which is the text the model reads
- [cosmetic] “destination_offers” added an optional parameter “from_date”
- [cosmetic] “destination_offers” added an optional parameter “to_date”
- [cosmetic] “search_venues” reworded the description of “at”
- [cosmetic] “search_venues” reworded the description of “open_now”
- [cosmetic] “search_venues” reworded the description of “open_on”

### 2026-10-30 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “list_cities” rewrote its description, which is the text the model reads
- [security] Tool “search_venues” rewrote its description, which is the text the model reads
- [cosmetic] “search_venues” reworded the description of “facets”
- [cosmetic] “search_venues” reworded the description of “prefer_facets”

### 2026-10-28 (score 75, +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.

### 2026-10-27 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.1.0 → 0.2.0

### 2026-10-26 (score 74)

First indexed and scored.

## MCP tools (17)

### `search` (~80 tokens)

Search everything by name

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.

Input parameters:

- `query` (string, required): A name or keywords, e.g. 'whale watching' or 'Acme Bistro'.

Output parameters:

- `reason` (string)
- `results` (array)
- `status` (string)

### `fetch` (~97 tokens)

Fetch a search result

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", "venue:acme-bistro:menu", "destination:los-cabos" or "listing:los-cabos:1234".

Input parameters:

- `id` (string, required): An id exactly as search returned it.

Output parameters:

- `id` (string)
- `metadata` (object)
- `reason` (string)
- `sample` (boolean)
- `status` (string)
- `text` (string)
- `title` (string)
- `url` (string)

### `search_venues` (~1089 tokens)

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 a name, a keyword or a short description. Each result has slug, capabilities, open_now and distance_km; a destination city's venues are here, its listings in destination_listings.

Input parameters:

- `accepts_reservations` (boolean|null): Set true to require venues that take reservations (a booking link or a live booking tool); omit otherwise.
- `at` (string|null): A local time (20:00 or 8pm) for the open_on filter; requires open_on.
- `avoid` (array): SOFT: venues matching these cuisine/neighbourhood tokens rank LOWER; not dropped.
- `city` (string|null): HARD filter: only venues in this city (case-insensitive); call list_cities for the exact values this directory knows.
- `cuisine` (string|null): HARD filter: only venues with this cuisine (case-insensitive exact match; a miss's reason lists the valid values).
- `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page.
- `facets` (array): HARD experiential-facet filter: each token is '<facet_type>:<value>' (e.g. 'dietary:vegetarian', 'view:sea'). A venue must match every facet_type given (values OR within a type); a miss EXCLUDES it.…
- `limit` (integer): Maximum number of items to return.
- `near` (string|null): HARD filter: only venues within radius_km of this 'latitude,longitude' point, nearest first, each with a distance_km; venues with no coordinates are excluded.
- `neighbourhood` (string|null): HARD filter: only venues in this neighbourhood (case-insensitive exact match; a miss's reason lists the valid values).
- `open_now` (boolean|null): Set true = open at this moment, not later today (venue local time, as open_now_at); for tonight use open_on=today with at; omit otherwise.
- `open_on`: HARD filter: only venues open on this weekday, or today/tomorrow in the venue's own timezone (optionally at 'at'); for tonight use open_on=today with at. Venues with no published hours are excluded.…
- `prefer_cuisine` (array): SOFT: venues of these cuisines rank higher; non-matches are NOT dropped.
- `prefer_facets` (array): SOFT experiential-facet preference, the same '<facet_type>:<value>' tokens and values as facets: a venue that declares them ranks higher but is NEVER dropped.
- `prefer_neighbourhood` (array): SOFT: venues in these neighbourhoods rank higher; non-matches are NOT dropped.
- `price_band` (string|null): HARD filter: only venues in this price band, e.g. '$$'.
- `query` (string|null): A name, a cuisine word or a short description of the place (e.g. 'quiet seafood with a sea view'); a dish is in search_menus. Venues whose name, description, cuisine, neighbourhood, city or alternate…
- `radius_km` (number|null): Search radius in km around 'near' (default applied when omitted).

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `list_cities` (~91 tokens)

List cities

List the cities that have published restaurants and bars. A city can also be a travel destination, such as Los Cabos: search_venues finds its venues, and destination_overview and destination_listings read the destination's own board.

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` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `search_menus` (~229 tokens)

Search menus across venues

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.

Input parameters:

- `allergens` (array): Exclude items that declare any of these allergens (spelling-insensitive; synonyms match: milk, lactose and dairy all match dairy; pass one term).
- `city` (string|null): 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.
- `max_price` (number|null): Only items priced at or under this, in the menu's currency.
- `query` (string|null): Text matched in item name, description, section and menu names; every word must match; connector words (and, with, in) aren't required.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `send_feedback` (~201 tokens)

Send feedback to Yenta

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.

Input parameters:

- `city` (string|null): The city the question was about; a city name only, never an address.
- `client` (string|null): The app or agent the model runs in.
- `kind` (string, required): What the report is about.
- `message` (string, required): The report itself, in plain words.
- `model` (string|null): The model sending the report, e.g. its model id.
- `purpose` (string|null): What the person was trying to do, in one short sentence.
- `subject` (string|null): The venue, destination or city the report is about, if any.
- `tool` (string|null): The Yenta tool the report is about, if any.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `venue_profile` (~110 tokens)

Venue profile by name or slug

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.

Input parameters:

- `city` (string|null): 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` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `venue_menu` (~303 tokens)

A venue's menu by name

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.

Input parameters:

- `allergens` (array): Exclude items declaring any of these allergens (case- and separator-insensitive (gluten free = gluten-free); synonyms match: milk, lactose and dairy all match dairy; pass one term).
- `city` (string|null): 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): A JSON array, e.g. ["gluten-free"]: items must carry ALL of these tags; case- and separator-insensitive (gluten free = gluten-free).
- `limit` (integer): Maximum number of items to return.
- `max_price` (number|null): Only items priced at or under this, in the menu's currency.
- `query` (string|null): Text matched in item name, description, section and menu names; every word must match; connector words (and, with, in) aren't required.
- `venue` (string, required): Venue name or slug; call search_venues to discover one.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `venue_faq` (~140 tokens)

Venue FAQ by name

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.

Input parameters:

- `city` (string|null): 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` (string|null): Text to match against questions and answers.
- `venue` (string, required): Venue name or slug; call search_venues to discover one.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `venue_events` (~202 tokens)

Search a venue's events by name

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.

Input parameters:

- `city` (string|null): 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.
- `event_type` (string|null): Exact event_type spelling from published events.
- `from_date` (string|null): ISO date; defaults to the venue's own local today, or to today UTC if it publishes no timezone.
- `limit` (integer): Maximum number of items to return.
- `to_date` (string|null): ISO date; omit to_date for everything upcoming (recommended for "coming up").
- `venue` (string, required): Venue name or slug; call search_venues to discover one.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `destination_overview` (~95 tokens)

Destination overview by name or slug

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. preview.complete is false when destination_listings / destination_events hold more.

Input parameters:

- `destination` (string, required): Destination name or slug, e.g. 'Los Cabos'; list_cities names them.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `destination_listings` (~345 tokens)

Search a destination's listings by name

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.

Input parameters:

- `area` (string|null): Area name or slug; destination_overview lists them.
- `category` (string|null): Category name or slug; destination_overview lists them.
- `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page.
- `destination` (string, required): Destination name or slug, e.g. 'Los Cabos'; list_cities names them.
- `language` (string|null): Language code (e.g. 'en', 'es'); defaults to the destination's.
- `limit` (integer): Maximum number of items to return.
- `listing_id` (string|null): One listing's id from a previous result: returns its full detail in item, ignoring the other filters; read a live linked_venue_slug with the venue_* tools, whose answer carries its booking link.
- `near_listing_id` (string|null): A listing id; returns listings within radius_km, nearest first, each with distance_km.
- `query` (string|null): Words matched in any order against listing names, descriptions, tags and categories.
- `radius_km` (number|null): 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` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `destination_events` (~212 tokens)

Search a destination's events by name

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's page.

Input parameters:

- `area` (string|null): Area name or slug; destination_overview lists them.
- `category` (string|null): Category name or slug; destination_overview lists them.
- `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page.
- `destination` (string, required): Destination name or slug, e.g. 'Los Cabos'; list_cities names them.
- `from_date` (string|null): ISO date; defaults to today.
- `limit` (integer): Maximum number of items to return.
- `query` (string|null): Words matched in any order against event names and descriptions.
- `to_date` (string|null): ISO date; omit to_date for everything upcoming (recommended for "coming up").

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `destination_guide` (~142 tokens)

Destination guides by name

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.

Input parameters:

- `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page.
- `destination` (string, required): Destination name or slug, e.g. 'Los Cabos'; list_cities names them.
- `limit` (integer|null): Entries per page; omit for the server's short default.
- `query` (string|null): Text to match in guide title/body.
- `topic`: Guide topic; omit for all.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `destination_faq` (~103 tokens)

Destination FAQ by name

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

Input parameters:

- `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page.
- `destination` (string, required): Destination name or slug, e.g. 'Los Cabos'; list_cities names them.
- `limit` (integer): Maximum number of items to return.
- `query` (string|null): Text to match in question/answer.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `destination_offers` (~242 tokens)

Search a destination's offers by name

Find a named destination's current deals and packages, with the partner booking link. Only offers valid on valid_on (today by default), or on any day from from_date to to_date, are returned. Results carry booking_url, the partner's booking page when present, and canonical_url, the destination's page.

Input parameters:

- `area` (string|null): Area name or slug; destination_overview lists them.
- `category` (string|null): Category name or slug; destination_overview lists them.
- `cursor` (integer): Number of items to skip; pass `next_cursor` from the previous page.
- `destination` (string, required): Destination name or slug, e.g. 'Los Cabos'; list_cities names them.
- `from_date` (string|null): ISO date; first day of a date range (defaults to today).
- `limit` (integer): Maximum number of items to return.
- `to_date` (string|null): ISO date; last day of the range; open-ended if omitted.
- `valid_on` (string|null): ISO date an offer must be valid on (valid_from to valid_through, inclusive); defaults to today.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

### `destination_seasonality` (~104 tokens)

Destination seasonality by name

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

Input parameters:

- `destination` (string, required): Destination name or slug, e.g. 'Los Cabos'; list_cities names them.
- `interest` (string|null): An activity or season, e.g. whales; keeps the months whose highlights or notes mention it.
- `month` (integer|null): 1-12; omit for all twelve.

Output parameters:

- `item` (object|null)
- `items` (array|null)
- `pagination` (object|null)
- `reason` (string|null)
- `sample` (boolean|null)
- `source` (object)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-yentaknows-directory/mcp#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74

## 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. Restaurants and bars in 10 cities: hours, menus, dietary tags, events and booking; destinations. This page covers its hosted endpoint (https://mcp.yentaknows.ai/mcp).

### Is the Yenta Directory MCP server safe to use?

Yenta Directory scores 78 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 17 tools: search, fetch, search_venues, list_cities, search_menus, and 12 more. Their descriptions and schemas cost roughly 3,785 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 5 November 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://mcp.yentaknows.ai/mcp
- Website: https://mcp.yentaknows.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-yentaknows-directory/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-yentaknows-directory/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-yentaknows-directory/mcp