Remote MCP · Endpoint

com.borisinc/aegis MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://aegis-mcp.borisinc.com/mcp

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

Registry name
com.borisinc/aegis
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
44.4% from 18 checks
Described by its publisher as
Trust layer for the x402 economy - check any service before you pay. Scores, discovery, routing.
Listing
From the official MCP registry (active).
Recent checks of com.borisinc/aegis
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoHandshake completed755 ms
4 days agoHandshake completed1.01 s
6 days agoHandshake completed940 ms
7 days agoHandshake completed824 ms
9 days agoHandshake completed805 ms
10 days agoHandshake completed791 ms
11 days agoHandshake completed816 ms
14 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed705 ms
17 days agoFailed - the server returned an HTTP error—
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
23 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—

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

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