MCP Tools
Servers → AnomalyArmor MCP

AnomalyArmor MCP · AnomalyArmor

Auth required
Unclaimed — claim this pagedeveloper-tools Auth expectations unknown
https://mcp.anomalyarmor.ai/mcp
Badge
Authentication requiredReachable; initialization requires authentication.
Since Aug 6, 2026 — 5:05 AM (43 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 error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\"",
  "discovery": {
    "resource": "https://mcp.anomalyarmor.ai/mcp",
    "authorization_servers": [
      "https://clerk.anomalyarmor.ai/"
    ],
    "scopes_supported": []
  }
}
100%
Availability · 30 days · 356 checks
191 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 2 h ago by MCP Tools Edge Scanner · scheduled every 120 min

Baseline captured — authentication required Informational Aug 6, 2026 — 5:05 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 error=\"invalid_token\", error_description=\"Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens.\", resource_metadata=\"https://mcp.anomalyarmor.ai/.well-known/oauth-protected-resource/mcp\"",
  "discovery": {
    "resource": "https://mcp.anomalyarmor.ai/mcp",
    "authorization_servers": [
      "https://clerk.anomalyarmor.ai/"
    ],
    "scopes_supported": []
  }
}
Observed by MCP Tools Edge Scanner