MCP Tools
Servers → BoundaryAI Runtime Safety MCP

BoundaryAI Runtime Safety MCP · BoundaryAI

Auth required
Unclaimed — claim this pageinfrastructure API key expected
https://mcp.boundaryai.ai/mcp
Badge
Authentication requiredReachable; initialization requires authentication.
Since Aug 6, 2026 — 5:15 AM (88 d ago)

An authentication challenge is availability, not an outage — the endpoint is reachable and answering. Passive observation records the challenge and any OAuth discovery metadata without ever authenticating. OAuth-authenticated contract monitoring is planned.

Recorded auth metadata
authMeta — as observed
{
  "httpStatus": 401,
  "wwwAuthenticate": "Bearer realm=\"boundaryai-mcp\"",
  "discovery": null
}
100%
Availability · 30 days · 350 checks
258 ms
Latency (last observation)
—
Contract
—
Schema stable
0
Incidents · 30 days
—
Observed since

Availability — last 30 days

No failures Some failures Mostly failing Auth required No observations

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

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": "Bearer realm=\"boundaryai-mcp\"",
  "discovery": null
}
Observed by MCP Tools Edge Scanner