Remote MCP · Endpoint

CorpusIQ MCP server

No. CorpusIQ answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp2.corpusiq.io/mcp

The last check completed an MCP handshake.

Registry name
io.corpusiq/multi-source-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
215 ms
Tools exposed
121 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Authenticated, user-scoped MCP connectors for 30+ business systems.
Listing
From the official MCP registry (active).
Recent checks of CorpusIQ
CheckedResultHandshake
1 hour agoHandshake completed215 ms
2 days agoHandshake completed192 ms
4 days agoHandshake completed210 ms
5 days agoHandshake completed220 ms
7 days agoHandshake completed240 ms
8 days agoHandshake completed188 ms
9 days agoHandshake completed192 ms
12 days agoHandshake completed202 ms
13 days agoHandshake completed197 ms
15 days agoHandshake completed200 ms
16 days agoHandshake completed196 ms
18 days agoHandshake completed218 ms
19 days agoHandshake completed192 ms
20 days agoHandshake completed220 ms
20 days agoHandshake completed210 ms
21 days agoHandshake completed188 ms
22 days agoHandshake completed235 ms

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