Remote MCP · Endpoint
SOC 2 Compared MCP server
Yes, as of 3 days ago: the server returned an HTTP error.
DownLast checked 3 days ago
Server URL
https://soc2compared.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.soc2compared/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 90.9% from 11 checks
- Described by its publisher as
- Look up year-one SOC 2 platform prices at 25 employees and the audit firms that issue reports.
- Website
- https://soc2compared.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Handshake completed | 917 ms |
| 16 days ago | Handshake completed | 334 ms |
| 17 days ago | Handshake completed | 346 ms |
| 18 days ago | Handshake completed | 339 ms |
| 19 days ago | Handshake completed | 365 ms |
| 21 days ago | Handshake completed | 340 ms |
| 21 days ago | Handshake completed | 344 ms |
| 22 days ago | Handshake completed | 327 ms |
| 24 days ago | Handshake completed | 348 ms |
| 26 days ago | Handshake completed | 368 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 SOC 2 Compared and makes no claim about it beyond what these checks measured.