Remote MCP · Endpoint
Yenta Directory MCP server
No. Yenta Directory answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://yentaknows.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.yentaknows/directory
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 806 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Anonymous, read-only cross-venue discovery of partner-approved venues, cities, destinations.
- Website
- https://yentaknows.ai/
- Repository
- https://github.com/yenta-ai/yenta-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 806 ms |
| 2 days ago | Handshake completed | 645 ms |
| 4 days ago | Handshake completed | 799 ms |
| 6 days ago | Handshake completed | 640 ms |
| 7 days ago | Handshake completed | 637 ms |
| 9 days ago | Handshake completed | 787 ms |
| 10 days ago | Handshake completed | 637 ms |
| 11 days ago | Handshake completed | 649 ms |
| 14 days ago | Handshake completed | 798 ms |
| 15 days ago | Handshake completed | 795 ms |
| 17 days ago | Handshake completed | 635 ms |
| 18 days ago | Handshake completed | 633 ms |
| 19 days ago | Handshake completed | 798 ms |
| 20 days ago | Handshake completed | 796 ms |
| 21 days ago | Handshake completed | 801 ms |
| 22 days ago | Handshake completed | 637 ms |
| 23 days ago | Handshake completed | 653 ms |
| 24 days ago | Handshake completed | 638 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Yenta Directory and makes no claim about it beyond what these checks measured.