Remote MCP · Endpoint
yesmcp MCP server
Yes, as of 1 hour ago: the TLS certificate could not be verified.
DownLast checked 1 hour ago
Server URL
https://mcp.yesmcp.com/mcp
The last check failed: the TLS certificate could not be verified.
- Registry name
- com.yesmcp/connector
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 22.2% from 18 checks
- Described by its publisher as
- See what an MCP connector can do for your business, get a scenario map, book a consultation.
- Website
- https://yesmcp.com/connect/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the TLS certificate could not be verified | — |
| 1 day ago | Failed - the TLS certificate could not be verified | — |
| 2 days ago | Failed - the TLS certificate could not be verified | — |
| 3 days ago | Failed - the TLS certificate could not be verified | — |
| 4 days ago | Failed - the TLS certificate could not be verified | — |
| 5 days ago | Failed - the TLS certificate could not be verified | — |
| 6 days ago | Failed - the TLS certificate could not be verified | — |
| 9 days ago | Failed - the TLS certificate could not be verified | — |
| 12 days ago | Failed - the TLS certificate could not be verified | — |
| 14 days ago | Failed - the TLS certificate could not be verified | — |
| 16 days ago | Failed - the TLS certificate could not be verified | — |
| 18 days ago | Failed - the TLS certificate could not be verified | — |
| 20 days ago | Failed - the TLS certificate could not be verified | — |
| 22 days ago | Failed - the TLS certificate could not be verified | — |
| 24 days ago | Handshake completed | 266 ms |
| 26 days ago | Handshake completed | 271 ms |
| 27 days ago | Handshake completed | 281 ms |
| 28 days ago | Handshake completed | 279 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 29.
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 yesmcp and makes no claim about it beyond what these checks measured.