Ambix MCP · Ambix

Auth required
Unclaimed — claim this pageproductivity Auth expectations unknown
https://mcp.ambix.ai
Badge
Authentication requiredReachable; initialization requires authentication.
Since Oct 25, 2026 — 12:00 AM (8 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 resource_metadata=\"https://mcp.ambix.ai/.well-known/oauth-protected-resource\", scope=\"read write\"",
  "discovery": {
    "resource": "https://mcp.ambix.ai/",
    "authorization_servers": [
      "https://auth.ambix.ai/"
    ],
    "scopes_supported": [
      "read",
      "write",
      "offline_access"
    ]
  }
}
99.14%
Availability · 30 days · 349 checks
1193 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 h ago by MCP Tools Edge Scanner · scheduled every 120 min

Recovery Oct 25, 2026 — 12:00 AM
Endpoint returned to service after 250 minutes.
VerifiedA successful observation followed a confirmed outage (result: auth_required).
Observed by MCP Tools Edge Scanner 4 h 10 m
Outage Oct 24, 2026 — 9:55 PM
HTTP 530 with content-type text/plain; charset=utf-8 — this does not look like an MCP endpoint.
VerifiedTwo consecutive observations failed (latest: not_mcp, HTTP 530).
InterpretationClients depending on this endpoint may currently be unable to connect.
Raw event details
{
  "result": "not_mcp",
  "error": "HTTP 530 with content-type text/plain; charset=utf-8 — this does not look like an MCP endpoint."
}
Observed by MCP Tools Edge Scanner
Authentication is now required Breaking Oct 23, 2026 — 12:10 AM
The endpoint stopped accepting unauthenticated initialization.
Verifiedinitialize returned HTTP 401.
InterpretationUnauthenticated clients can no longer connect and may require credentials or an OAuth flow.
Raw event details
{
  "httpStatus": 401,
  "wwwAuthenticate": "Bearer resource_metadata=\"https://mcp.ambix.ai/.well-known/oauth-protected-resource\", scope=\"read write\"",
  "discovery": {
    "resource": "https://mcp.ambix.ai/",
    "authorization_servers": [
      "https://auth.ambix.ai/"
    ],
    "scopes_supported": [
      "read",
      "write",
      "offline_access"
    ]
  }
}
Observed by MCP Tools Edge Scanner
Authentication is now required Breaking Aug 11, 2026 — 2:25 AM
The endpoint stopped accepting unauthenticated initialization.
Verifiedinitialize returned HTTP 401.
InterpretationUnauthenticated clients can no longer connect and may require credentials or an OAuth flow.
Raw event details
{
  "httpStatus": 401,
  "wwwAuthenticate": "Bearer resource_metadata=\"https://mcp.ambix.ai/.well-known/oauth-protected-resource\", scope=\"read write\"",
  "discovery": {
    "resource": "https://mcp.ambix.ai",
    "authorization_servers": [
      "https://auth.ambix.ai/"
    ],
    "scopes_supported": [
      "read",
      "write",
      "offline_access"
    ]
  }
}
Observed by MCP Tools Edge Scanner
Baseline captured — authentication required Informational Aug 6, 2026 — 5:40 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 resource_metadata=\"https://mcp.ambix.ai/.well-known/oauth-protected-resource\", scope=\"read write\"",
  "discovery": {
    "resource": "https://mcp.ambix.ai",
    "authorization_servers": [
      "https://auth.ambix.ai/"
    ],
    "scopes_supported": [
      "read",
      "write",
      "offline_access"
    ]
  }
}
Observed by MCP Tools Edge Scanner