Remote MCP · Endpoint
com.webmcp-tool/agent-readiness MCP server
No. com.webmcp-tool/agent-readiness answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://webmcp-tool.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.webmcp-tool/agent-readiness
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 288 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Scores any public website on how usable it is by AI agents, with per-check evidence.
- Website
- https://webmcp-tool.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 288 ms |
| 2 days ago | Handshake completed | 283 ms |
| 4 days ago | Handshake completed | 288 ms |
| 5 days ago | Handshake completed | 290 ms |
| 7 days ago | Handshake completed | 285 ms |
| 8 days ago | Handshake completed | 287 ms |
| 9 days ago | Handshake completed | 282 ms |
| 12 days ago | Handshake completed | 265 ms |
| 13 days ago | Handshake completed | 288 ms |
| 15 days ago | Handshake completed | 328 ms |
| 16 days ago | Handshake completed | 294 ms |
| 18 days ago | Handshake completed | 286 ms |
| 19 days ago | Handshake completed | 284 ms |
| 20 days ago | Handshake completed | 298 ms |
| 20 days ago | Handshake completed | 327 ms |
| 21 days ago | Handshake completed | 287 ms |
| 22 days ago | Handshake completed | 286 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 com.webmcp-tool/agent-readiness and makes no claim about it beyond what these checks measured.