Semgrep MCP · Semgrep

Auth required
Unclaimed — claim this pagedeveloper-tools OAuth expected
https://mcp.semgrep.ai/mcp Docs
Badge
Authentication requiredReachable; initialization requires authentication.
Since Aug 20, 2026 — 5:55 AM (29 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 required\", resource_metadata=\"https://mcp.semgrep.ai/.well-known/oauth-protected-resource\"",
  "discovery": {
    "resource": "https://mcp.semgrep.ai/",
    "authorization_servers": [
      "https://login.semgrep.dev/"
    ],
    "scopes_supported": []
  }
}
99.85%
Availability · 30 days · 674 checks
295 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 24 min ago by MCP Tools Edge Scanner · scheduled every 60 min

Authentication is now required Breaking Aug 20, 2026 — 5:55 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 error=\"invalid_token\", error_description=\"Authentication required\", resource_metadata=\"https://mcp.semgrep.ai/.well-known/oauth-protected-resource\"",
  "discovery": {
    "resource": "https://mcp.semgrep.ai/",
    "authorization_servers": [
      "https://login.semgrep.dev/"
    ],
    "scopes_supported": []
  }
}
Observed by MCP Tools Edge Scanner
Authentication is now required Breaking Aug 17, 2026 — 10:30 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 error=\"invalid_token\", error_description=\"Authentication required\", resource_metadata=\"https://mcp.semgrep.ai/.well-known/oauth-protected-resource\"",
  "discovery": {
    "resource": "https://mcp.semgrep.ai/",
    "authorization_servers": [
      "https://login.semgrep.dev/"
    ],
    "scopes_supported": []
  }
}
Observed by MCP Tools Edge Scanner
Baseline captured — authentication required Informational Aug 6, 2026 — 5:10 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 required\", resource_metadata=\"https://mcp.semgrep.ai/.well-known/oauth-protected-resource\"",
  "discovery": {
    "resource": "https://mcp.semgrep.ai/",
    "authorization_servers": [
      "https://login.semgrep.dev/"
    ],
    "scopes_supported": []
  }
}
Observed by MCP Tools Edge Scanner