MCP Identity Gateway raises fanout timeout defaults
MCP Identity Gateway 1.34.5733 raises how long the Gateway waits for your assigned MCP servers when it fans a request out to them. The earlier defaults were short enough that a server still starting up, or one answering from a cold cache, could run past them.
| Timeout | 1.33.5654 | 1.34.5733 |
|---|---|---|
initialize | 3s | 10s |
notifications_initialized | 500ms | 1s |
tools_list | 1s | 3s |
proactive_tools_list | 3s | 5s |
resources_list | 1s | 3s |
reinit_initialize | 10s | 10s |
reinit_notifications_initialized | 500ms | 1s |
reinit_tools_list | 1s | 5s |
reinit_initialize is the one timeout this build leaves unchanged.
The new defaults require no configuration and apply to both deployment models as soon as you upgrade. They’re high enough that an AI client typically reaches its own timeout before the Gateway reaches one of these, so most deployments never need to change them.
A self-hosted Gateway can override any of these timeouts as a last resort, using the
AEMBIT_MCP_GATEWAY_TIMEOUT environment variable.
The installer doesn’t forward this variable to the running service, so setting it takes a systemd drop-in.
For the accepted names, the value format, and the drop-in, see
MCP Identity Gateway environment variables.
Aembit sets these values for you on the Aembit-managed service.
These updates shipped in the same build as the MCP Identity Gateway 1.34.5733 release.