Remote MCP · Endpoint

ECCA MCP server

No. ECCA answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://eccaai.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.eccaai/ecca
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
206 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Compare engine claims, inspect dissent and check study evidence for student questions.
Website
https://eccaai.com/developers#code-mcp
Listing
From the official MCP registry (active).
Recent checks of ECCA
CheckedResultHandshake
1 hour agoHandshake completed206 ms
17 hours agoHandshake completed208 ms
1 day agoHandshake completed150 ms
3 days agoHandshake completed199 ms
5 days agoHandshake completed159 ms
7 days agoHandshake completed167 ms
10 days agoHandshake completed186 ms
12 days agoHandshake completed160 ms
14 days agoHandshake completed136 ms
16 days agoHandshake completed266 ms
18 days agoHandshake completed88 ms
20 days agoHandshake completed137 ms
22 days agoHandshake completed104 ms
23 days agoHandshake completed112 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with ECCA and makes no claim about it beyond what these checks measured.