Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

MCP Gateway Registry 1.37 tightens wildcards

Written November 12, 2026

If your team runs the community MCP Gateway Registry, the 1.37.0 upgrade changes what a wildcard grant actually grants, and moves every session cookie setting out of a config file into the environment. Both changes fail loudly for some deployments and silently for others — the notes tell you which is which, and what to set instead.

The wildcard no longer covers every method

The headline breaking change in the 1.37.0 release notes: a scope with tools: ["*"] used to grant broadly; it now grants every tool for tools/call and no other method. A custom scope that quietly relied on the wildcard for a method it never listed — resources/read or prompts/get, say — gets a 403 for that method until the method is added to the scope's methods list. The unrestricted seed scopes and the example scope files already list resources/read, prompts/list and prompts/get, so stock setups are covered; hand-written scopes are the ones to audit. The upgrade FAQ's Check your scopes section walks through finding affected groups and reading the refusals.

Logins and sessions get stricter

Two more breaking changes sit in the same upgrade. An OIDC login — Keycloak, Cognito, Entra, Okta, Auth0, PingFederate, or any flow whose token response carries an id_token — now fails with a 401 when it yields no account subject, a subject that is not a string, or one starting with name:. It used to succeed with a warning. The notes tell operators to search the auth-server logs for the old yielded-no-subject line before upgrading, so the failures are found on paper first. And session settings move house: the auth server refuses to start if the session block in auth_server/oauth2_providers.yml has been edited. Every cookie setting now comes from shared environment variables — SESSION_COOKIE_SECURE, SESSION_MAX_AGE_SECONDS, SESSION_COOKIE_NAME, SESSION_COOKIE_DOMAIN — and the startup error names each offending key and the variable to set. On Helm, the same values move to stack globals, and a render fails when a subchart value disagrees with them. One consequence worth knowing: SESSION_COOKIE_SECURE=false now actually takes effect on HTTPS, where the config file's true used to win; both services warn about it at startup.

Also in the notes

The release adds support for the MCP 2026-07-28 specification and moves the registry's discovery, health probe, security scanner and gateway onto MCP SDK 2.x. Request bodies up to 1 MB are now authorized, where tool calls above about 10 KB used to fail with a 500. A refused MCP request now returns a JSON-RPC error with code -32003 naming the refused method, the tool and the server, instead of a bare forbidden message — which makes the wildcard refusals above debuggable from the client side. Browser-session MCP requests must also carry the gateway's own origin. And /branding is now a reserved path, so a server or agent registered under it will fail; existing registrations need a look before upgrading.

Verdict

Tighten your wildcard grants on upgrade: list the methods each scope truly needs, because after 1.37.0 the wildcard no longer lists them for you.

Limits

Related playbooks

Sources

Back to: Coding tasks playbooks hub · Also: MCP's July spec killed sessions — tooling may not know · MCPhantom: agents install dead MCP servers · DeepSeek's Super-Agent is a prototype — treat it that way · Patch your MCP reference servers now · MCP now ships on a six-month clock