Remote MCP · Endpoint

AegisAI MCP server

No. AegisAI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aegis-api.kadopi.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.kadopi/aegis-ai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.37 s
Tools exposed
17 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Paid pre-execution risk verification for AI agents over MCP and x402.
Listing
From the official MCP registry (active).
Recent checks of AegisAI
CheckedResultHandshake
1 hour agoHandshake completed3.37 s
2 days agoHandshake completed310 ms
4 days agoHandshake completed441 ms
5 days agoHandshake completed437 ms
7 days agoHandshake completed513 ms
8 days agoHandshake completed589 ms
9 days agoHandshake completed208 ms
12 days agoHandshake completed401 ms
13 days agoHandshake completed247 ms
15 days agoHandshake completed205 ms
17 days agoHandshake completed301 ms
18 days agoHandshake completed269 ms
19 days agoHandshake completed250 ms
20 days agoHandshake completed230 ms
20 days agoHandshake completed213 ms
21 days agoHandshake completed207 ms
23 days agoHandshake completed259 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 AegisAI and makes no claim about it beyond what these checks measured.