Remote MCP · Endpoint

AgentAegis MCP server

Yes, as of 6 days ago: the server returned an HTTP error.

DownLast checked 6 days ago

Server URL

https://agentaegis-mcp-production.up.railway.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.astafford8488/agentaegis
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
28 tools
Uptime, last 30 days
53.3% from 15 checks
Described by its publisher as
Pay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security.
Listing
From the official MCP registry (active).
Recent checks of AgentAegis
CheckedResultHandshake
6 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed38 ms
15 days agoHandshake completed42 ms
18 days agoHandshake completed44 ms
20 days agoHandshake completed26 ms
22 days agoHandshake completed35 ms
25 days agoHandshake completed28 ms
27 days agoHandshake completed22 ms
29 days agoHandshake completed27 ms
31 days agoHandshake completed26 ms
33 days agoHandshake completed21 ms
34 days agoHandshake completed38 ms
36 days agoHandshake completed27 ms

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

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