Remote MCP · Endpoint

SpecProof MCP server

No. SpecProof answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.specproof.ai/

The last check completed an MCP handshake.

Registry name
ai.specproof/specproof-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
17 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
SpecProof: Search standards specs with MCP-ready precision.
Listing
From the official MCP registry (active).
Recent checks of SpecProof
CheckedResultHandshake
8 hours agoHandshake completed111 ms
2 days agoHandshake completed110 ms
4 days agoHandshake completed111 ms
5 days agoFailed - the connection was refused or dropped—
7 days agoHandshake completed132 ms
8 days agoHandshake completed117 ms
9 days agoHandshake completed109 ms
12 days agoHandshake completed120 ms
13 days agoHandshake completed114 ms
15 days agoHandshake completed111 ms
16 days agoHandshake completed139 ms
17 days agoHandshake completed142 ms
18 days agoHandshake completed139 ms
19 days agoHandshake completed135 ms
20 days agoHandshake completed136 ms
21 days agoHandshake completed138 ms
23 days agoHandshake completed130 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 SpecProof and makes no claim about it beyond what these checks measured.