Amazon Bedrock AgentCore Gateway: How to Inspect the MCP OAuth Setup (JWT Authorizer, Cognito, Okta, RFC 9728, CloudFront) A new technical walkthrough documents how to inspect the OAuth setup of an Amazon Bedrock AgentCore Gateway MCP endpoint, covering the four inbound authorization modes — CUSTOM_JWT, IAM, AUTHENTICATE_ONLY and NONE — and the discovery chain a JWT-protected gateway exposes to unauthenticated callers. The guide, based on AWS's AgentCore Gateway inbound authorization documentation, shows that a CUSTOM_JWT gateway returns a 401 with a WWW-Authenticate header carrying resource_metadata and scope parameters per RFC 6750, and that a valid token missing required scopes gets a 403 with error="insufficient_scope". It warns that a gateway configured with authorizerType NONE answers tools/list anonymously and enforces nothing unless authorization is handled by a policy engine, interceptor Lambda function or the downstream target. Amazon Bedrock AgentCore Gateway: How to Inspect the MCP OAuth Setup JWT Authorizer, Cognito, Okta, RFC 9728, CloudFront Check an Amazon Bedrock AgentCore Gateway MCP endpoint's OAuth setup: Cognito, Okta, Auth0 or Entra ID JWT authorizers, RFC 9728 metadata, CloudFront domainOverride. Amazon Bedrock AgentCore Gateway turns APIs, Lambda functions and other targets into a single MCP endpoint that agents can call. Every gateway is a remote MCP server, and every remote MCP server has the same first question: what does it say to a caller who shows up with no token? This post maps the four inbound authorization modes of AgentCore Gateway to what an outside caller can observe, walks the OAuth discovery chain for a JWT-protected gateway with curl , and lists the checks worth running before you hand the gateway URL to an agent. It is based on the AgentCore Gateway inbound authorization documentation https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-inbound-auth.html ; check that page for the current field names, since the service is new and changes quickly. The gateway endpoint An AWS-managed gateway URL has this shape: https://