Remote MCP · Endpoint

Corpus Plan MCP server

No. Corpus Plan answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://plan.corpushq.co/mcp

The last check completed an MCP handshake.

Registry name
co.corpushq.plan/corpus-plan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free SEO/GEO audits of public websites and AI answer-engine citation checks. No login or API key.
Listing
From the official MCP registry (active).
Recent checks of Corpus Plan
CheckedResultHandshake
52 minutes agoHandshake completed172 ms
3 days agoHandshake completed51 ms
12 days agoHandshake completed56 ms
13 days agoHandshake completed63 ms
14 days agoHandshake completed853 ms
15 days agoHandshake completed67 ms
17 days agoHandshake completed83 ms
18 days agoHandshake completed111 ms
18 days agoHandshake completed68 ms
20 days agoHandshake completed158 ms
22 days agoHandshake completed57 ms
25 days agoHandshake completed199 ms
27 days agoHandshake completed183 ms
29 days agoHandshake completed328 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

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 Corpus Plan and makes no claim about it beyond what these checks measured.