MatrixRecord of · MCP Authorization 2026-07-28

Datadog

How it meets the 23 requirements of MCP Authorization.

Supported
9
Unsupported
4
Unknown, recorded
1
Not observed yet
9
Endpoint
https://mcp.datadoghq.com/v1/mcp
Transport
Streamable HTTP
Access
Unknown nobody has stated this yet
Auth
OAuth An OAuth 2.x authorization obtained through the server's authorization server. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · OAuth 2.0 is the recommended method and follows the MCP authorization specification; a personal or service access token as bearer header is the fallback. Redirect URLs of new OAuth clients are allow-listed in Organization Settings.
Why it is listed
Added by the atlas maintainer from the vendor's own documentation. Source
Homepage
https://www.datadoghq.com
Notes
One endpoint per Datadog site; EU1 is https://mcp.datadoghq.eu/v1/mcp. The atlas lists US1. MCP access is an organization setting, and the docs do not say whether every plan has it, so the access class is left open.

Against MCP Authorization 2026-07-28current

  • Supported 9
  • Unsupported 4
  • Unknown 10

Passive scan · Requests

  • MUST8 supported
  • SHOULD3 unsupported, 1 unknown
  • MAY1 supported, 1 unsupported

Contribute a correctionWithdraw this serverJSON

Older revisions of the matrix: 2025-11-25

MCP server features 13

FeatureLevelStatusObservedEvidence
Protected Resource Metadata servedmcp.prm · Discovery · Authorization Server Discovery › Authorization Server LocationMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; resource: https://mcp.datadoghq.com/v1/mcp
PRM lists an authorization servermcp.prm.authorization-servers · Discovery · Authorization Server Discovery › Authorization Server LocationMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; authorization_servers: [https://mcp.datadoghq.com/v1/mcp]
PRM lists scopes_supportedmcp.prm.scopes-supported · Discovery · Authorization › Scope Selection StrategyMAYUnsupportedPassive scan · scanner@0.4.0source— HTTP 200; scopes_supported: absent
PRM reachable at a well-known URImcp.prm.well-known · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; found at the path-aware location
resource_metadata in the 401 challengemcp.prm.www-authenticate · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 401; WWW-Authenticate resource_metadata: https://mcp.datadoghq.com/.well-known/oauth-protected-resource/v1/mcp
403 insufficient_scope for step-upmcp.rs.insufficient-scope · Authorization · Authorization › Scope Challenge HandlingSHOULDUnknown no observationno observation yet
Scope in the WWW-Authenticate challengemcp.rs.scope-challenge · Authorization · Authorization › Scope Selection StrategySHOULDUnsupportedPassive scan · scanner@0.4.0source— HTTP 401; WWW-Authenticate: Bearer resource_metadata="https://mcp.datadoghq.com/.well-known/oauth-protected-resource/v1/mcp", no scope parameter
No offline_access in advertised scopesmcp.prm.no-offline-access · Tokens · Authorization › Refresh TokensSHOULDUnknownPassive scan · scanner@0.4.0source— HTTP 200; scopes_supported: absent, so no scope is advertised to judge
401 for missing or invalid tokensmcp.rs.401-on-invalid · Tokens · Authorization › Token HandlingMUSTUnknown no observationno observation yet
Audience validationmcp.rs.audience-validation · Tokens · Security Considerations › Access Token Privilege RestrictionMUSTUnknown no observationno observation yet
Bearer token only in the Authorization headermcp.rs.bearer-header · Tokens · Authorization › Access Token UsageMUSTUnknown no observationno observation yet
No token passthrough to upstream APIsmcp.rs.no-passthrough · Delegation · Security Considerations › Access Token Privilege RestrictionMUSTUnknown no observationno observation yet
Per-client consent on proxy serversmcp.proxy.consent · Consent · Security Considerations › Confused Deputy ProblemMUSTUnknown no observationno observation yet

Authorization server features 10

FeatureLevelStatusObservedEvidence
Metadata issuer matches the discovery URLmcp.as.issuer-match · Discovery · Authorization Server Discovery › Authorization Server Metadata DiscoveryMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; issuer: https://mcp.datadoghq.com/v1/mcp equals the issuer the PRM named
Authorization server metadata discoverablemcp.as.metadata · Discovery · Authorization Server Discovery › Authorization Server Metadata DiscoveryMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; issuer: https://mcp.datadoghq.com/v1/mcp
Client ID Metadata Documents supportedmcp.as.cimd · Registration · Client Registration › Client ID Metadata DocumentsSHOULDUnsupportedPassive scan · scanner@0.4.0source— HTTP 200; client_id_metadata_document_supported: absent
Dynamic Client Registration offeredmcp.as.dcr · Registration · Client Registration › Dynamic Client RegistrationMAYSupportedPassive scan · scanner@0.4.0source— HTTP 200; registration_endpoint: https://app.datadoghq.com/api/v2/oauth2/register
Documented pre-registration pathmcp.as.preregistration · Registration · Client Registration › Pre-registrationSHOULDUnknown no observationno observation yet
Issuer identifier in authorization responsesmcp.as.iss-param · Authorization · Authorization › Authorization Response ValidationSHOULDUnsupportedPassive scan · scanner@0.4.0source— HTTP 200; authorization_response_iss_parameter_supported: absent
PKCE with S256 advertisedmcp.as.pkce-s256 · Authorization · Security Considerations › Authorization Code ProtectionMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; code_challenge_methods_supported: [S256]
Refresh token rotation for public clientsmcp.as.refresh-rotation · Tokens · Security Considerations › Token TheftMUSTUnknown no observationno observation yet
Resource indicators honouredmcp.as.resource-indicator · Tokens · Security Considerations › Token Audience Binding and ValidationMUSTUnknown no observationno observation yet
All endpoints served over HTTPSmcp.as.https · Transport · Security Considerations › Communication SecurityMUSTSupportedPassive scan · scanner@0.4.0source— HTTP 200; all 3 endpoints use https

This server's ledger

No status change on record

Every cell of this server still shows the status of its first observation.

The whole ledger

What the scanner asked

The requests behind the rows marked passive scan above, in the order the scanner makes them, each with the newest answer recorded. None carries a credential or a message.

  1. GEThttps://mcp.datadoghq.com/.well-known/oauth-protected-resource/v1/mcpHTTP 200read resource, authorization_servers, scopes_supported
  2. GEThttps://mcp.datadoghq.com/v1/mcpHTTP 401read status, WWW-Authenticate
  3. GEThttps://mcp.datadoghq.com/.well-known/oauth-authorization-server/v1/mcpHTTP 200read issuer, client_id_metadata_document_supported, registration_endpoint, authorization_response_iss_parameter_supported, code_challenge_methods_supported
  4. 14 checks, read into the tables above

Newest scanner observation · letsauth-scanner/0.4.0 · reproduce with pnpm scan datadog · scan JSON · data file · how the scanner works