Remote MCP · Endpoint
SRI — MCP Server Inspector MCP server
No. SRI — MCP Server Inspector answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://sri-test.biz/mcp
The last check completed an MCP handshake.
- Registry name
- biz.sri-test/verifier
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 769 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- 2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
- Website
- https://sri-test.biz/
- Repository
- https://github.com/SRITEST0001/sri
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 769 ms |
| 1 day ago | Handshake completed | 623 ms |
| 2 days ago | Handshake completed | 626 ms |
| 3 days ago | Handshake completed | 642 ms |
| 4 days ago | Handshake completed | 579 ms |
| 5 days ago | Handshake completed | 600 ms |
| 7 days ago | Handshake completed | 567 ms |
| 10 days ago | Handshake completed | 679 ms |
| 12 days ago | Handshake completed | 613 ms |
| 15 days ago | Handshake completed | 711 ms |
| 17 days ago | Handshake completed | 681 ms |
| 19 days ago | Handshake completed | 582 ms |
| 21 days ago | Handshake completed | 552 ms |
| 23 days ago | Handshake completed | 668 ms |
| 25 days ago | Handshake completed | 736 ms |
| 26 days ago | Handshake completed | 585 ms |
| 28 days ago | Handshake completed | 653 ms |
| 29 days ago | Handshake completed | 605 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 SRI — MCP Server Inspector and makes no claim about it beyond what these checks measured.