Remote MCP · Endpoint
Testsy MCP server
No. Testsy answered an MCP handshake 18 minutes ago.
UpLast checked 18 minutes ago
Server URL
https://app.testsy.dev/mcp
The last check completed an MCP handshake.
- Registry name
- dev.testsy/testsy
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 464 ms
- Tools exposed
- 48 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Run plain-English web QA tests and inspect check results and evidence.
- Website
- https://testsy.dev/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 18 minutes ago | Handshake completed | 464 ms |
| 9 days ago | Credentials required | — |
| 9 days ago | Credentials required | — |
| 11 days ago | Credentials required | — |
| 12 days ago | Credentials required | — |
| 13 days ago | Credentials required | — |
| 14 days ago | Credentials required | — |
| 14 days ago | Credentials required | — |
| 16 days ago | Credentials required | — |
| 19 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 Testsy and makes no claim about it beyond what these checks measured.