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.
Listing
From the official MCP registry (active).
Recent checks of SOC 2 Compared
CheckedResultHandshake
3 days agoFailed - the server returned an HTTP error—
7 days agoHandshake completed917 ms
16 days agoHandshake completed334 ms
17 days agoHandshake completed346 ms
18 days agoHandshake completed339 ms
19 days agoHandshake completed365 ms
21 days agoHandshake completed340 ms
21 days agoHandshake completed344 ms
22 days agoHandshake completed327 ms
24 days agoHandshake completed348 ms
26 days agoHandshake completed368 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.