AI Security Gateway MCP · AI Security Gateway

Not responding as MCP
Unclaimed — claim this pageinfrastructure API key expected
https://api.aisecuritygateway.ai/mcp
Badge
Not responding as MCPHTTP 503 with content-type text/html — this does not look like an MCP endpoint.
Since Sep 10, 2026 — 1:01 AM (8 d ago)
96.4%
Availability · 30 days · 275 checks
126 ms
Latency (last observation)
Contract
Schema stable
1
Incidents · 30 days
Observed since

Availability — last 30 days

No failures Some failures Mostly failing Auth required No observations

Last observed 1 d ago by MCP Tools Edge Scanner · scheduled every 120 min

Outage Sep 10, 2026 — 3:05 AM
HTTP 503 with content-type text/html — this does not look like an MCP endpoint.
VerifiedTwo consecutive observations failed (latest: not_mcp, HTTP 503).
InterpretationClients depending on this endpoint may currently be unable to connect.
Raw event details
{
  "result": "not_mcp",
  "error": "HTTP 503 with content-type text/html — this does not look like an MCP endpoint."
}
Observed by MCP Tools Edge Scanner
Baseline captured — authentication required Informational Aug 6, 2026 — 5:15 AM
Endpoint is reachable; initialization requires authentication. Passive observation records availability, latency, and protocol behavior only.
Verifiedinitialize returned HTTP 401.
InterpretationAuthenticated contract monitoring can be added later (OAuth support planned).
Raw event details
{
  "httpStatus": 401,
  "wwwAuthenticate": null,
  "discovery": null
}
Observed by MCP Tools Edge Scanner