Sign-in required, tools not seen, not counted. The MCP endpoint listed for Datadog at mcp.datadoghq.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.
69, grade C; Ora scanned the domain on 15 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for datadoghq.com, a vendor-published score)
Company found through
the vendor's own documentation; Ora's public leaderboard
The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.
Connector log
2 connections on 4 November 2026, read-only methods only
19:55:53Z https://mcp.datadoghq.com/api/unstable/mcp-server/mcp sent initialize result auth-required (HTTP 401) 1031 ms
20:01:29Z https://mcp.datadoghq.com/api/unstable/mcp-server/mcp sent initialize result auth-required (HTTP 401) 1102 ms
Request https://mcp.datadoghq.com/api/unstable/mcp-server/mcp without a token. It answers 401 and a WWW-Authenticate header.
Read the protected resource metadata at https://mcp.datadoghq.com/.well-known/oauth-protected-resource/api/unstable/mcp-server/mcp to find the authorization server.
Register a client at the registration endpoint https://app.datadoghq.com/api/v2/oauth2/register (dynamic client registration), so no human has to create an app first.
Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.