letsauth

Server

AWS Knowledge

by AWS

Endpoint
https://knowledge-mcp.global.api.aws
Transport
Streamable HTTP
Authentication as listed
open (the source's own label, not an observation)
Why it is listed
Listed because it appears in a public directory of MCP servers. Source
Homepage
https://aws.github.io/
  • Not applicable 23

Contribute a correctionWithdraw this serverJSON

Status against MCP Authorization 2026-07-28 (current revision). Older revisions: 2025-11-25

MCP server features

FeatureLevelStatusObservedEvidence
Protected Resource Metadata servedmcp.prm · Discovery · Authorization Server Discovery › Authorization Server LocationMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
PRM lists an authorization servermcp.prm.authorization-servers · Discovery · Authorization Server Discovery › Authorization Server LocationMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
PRM lists scopes_supportedmcp.prm.scopes-supported · Discovery · Authorization › Scope Selection StrategyMAYNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
PRM reachable at a well-known URImcp.prm.well-known · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
resource_metadata in the 401 challengemcp.prm.www-authenticate · Discovery · Authorization Server Discovery › Protected Resource Metadata Discovery RequirementsMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
403 insufficient_scope for step-upmcp.rs.insufficient-scope · Authorization · Authorization › Scope Challenge HandlingSHOULDNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Scope in the WWW-Authenticate challengemcp.rs.scope-challenge · Authorization · Authorization › Scope Selection StrategySHOULDNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
No offline_access in advertised scopesmcp.prm.no-offline-access · Tokens · Authorization › Refresh TokensSHOULDNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
401 for missing or invalid tokensmcp.rs.401-on-invalid · Tokens · Authorization › Token HandlingMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Audience validationmcp.rs.audience-validation · Tokens · Security Considerations › Access Token Privilege RestrictionMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Bearer token only in the Authorization headermcp.rs.bearer-header · Tokens · Authorization › Access Token UsageMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
No token passthrough to upstream APIsmcp.rs.no-passthrough · Delegation · Security Considerations › Access Token Privilege RestrictionMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Per-client consent on proxy serversmcp.proxy.consent · Consent · Security Considerations › Confused Deputy ProblemMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.

Authorization server features

FeatureLevelStatusObservedEvidence
Metadata issuer matches the discovery URLmcp.as.issuer-match · Discovery · Authorization Server Discovery › Authorization Server Metadata DiscoveryMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Authorization server metadata discoverablemcp.as.metadata · Discovery · Authorization Server Discovery › Authorization Server Metadata DiscoveryMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Client ID Metadata Documents supportedmcp.as.cimd · Registration · Client Registration › Client ID Metadata DocumentsSHOULDNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Dynamic Client Registration offeredmcp.as.dcr · Registration · Client Registration › Dynamic Client RegistrationMAYNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Documented pre-registration pathmcp.as.preregistration · Registration · Client Registration › Pre-registrationSHOULDNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Issuer identifier in authorization responsesmcp.as.iss-param · Authorization · Authorization › Authorization Response ValidationSHOULDNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
PKCE with S256 advertisedmcp.as.pkce-s256 · Authorization · Security Considerations › Authorization Code ProtectionMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Refresh token rotation for public clientsmcp.as.refresh-rotation · Tokens · Security Considerations › Token TheftMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
Resource indicators honouredmcp.as.resource-indicator · Tokens · Security Considerations › Token Audience Binding and ValidationMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.
All endpoints served over HTTPSmcp.as.https · Transport · Security Considerations › Communication SecurityMUSTNot applicableVendor claim · jbspeakrsourcelists the server as Open; no OAuth authorization server is involved.