Improved MCP Identity Gateway token, credential, and error handling

October 14, 2026

MCP Identity Gateway version 1.35.6086 accepts more access token audiences and sends credentials in named headers. It also reports more detail when an MCP server or a CrowdStrike AIDR inspection fails.

For the latest available versions of these components, see the Edge Components Supported Versions page.

Access token audience: MCP Identity Gateway accepts an access token whose audience is its /mcp endpoint URL with a trailing slash. See Token and credential details.
Credentials in a named header: When a Server Workload uses the Header authentication scheme, MCP Identity Gateway sends the credential to the MCP server in the header you name. MCP servers that take an API key in a custom header now receive it. See Authentication sent to the MCP server.
Longer list timeouts: The default tools_list, resources_list, and prompts_list timeouts are 5 seconds, up from 3 seconds. See AEMBIT_MCP_GATEWAY_TIMEOUT.
CrowdStrike AIDR timeouts in workload events: When a CrowdStrike AIDR inspection request times out, the workload event’s error message says so and gives the timeout. See Fail-open and fail-closed behavior.
MCP server connection errors: When MCP Identity Gateway can’t connect to the MCP server for a request such as tools/call, the MCP client gets error -32603. The error message names the failure, such as failed to connect to upstream MCP server. When the MCP server answered with an HTTP status, the error’s data carries it in upstreamHttpStatus, which replaces the status field that earlier versions sent. Update any client code that reads status.
Workload events for each MCP server: For tools/list, resources/list, and prompts/list, MCP Identity Gateway now emits a request event for each MCP server it fans the request out to. This includes a server it then skips because that server doesn’t support the method. These request events, and the event for each MCP server that fails, now name the Server Workload. A failure event also records the MCP server’s host and HTTP status when known. Review retention and alerting thresholds for the added request events. See Requests that fan out to multiple servers.

This build also adds change notifications and tool output validation and a security update.

Tags:

← Back to changelog