github agentic-community/mcp-gateway-registry 1.38.1
1.38.1 - Faster Virtual Server Discovery

one hour ago

Release 1.38.1 - Faster Virtual Server Discovery

November 2026


Upgrading from 1.38.0

This section covers everything you need to know to upgrade from 1.38.0 to 1.38.1.

Breaking Changes

There are no breaking changes in this release.

Other upgrade notes

  • Virtual servers stop advertising prompts. initialize and server/discover advertise tools, plus resources only when a mapped tool opens an MCP App page. A client that sends prompts/list anyway still gets an answer. (#2086)
  • Servers that answer the health check with 401 or 403 show as healthy-auth-expired. They used to show as healthy. The status still routes, on direct routes and virtual servers alike, and the registry no longer schedules tool fetches for these servers, which failed anyway. This ends the workaround tracked in #167. (#2086)
  • Virtual servers leave out backing servers the gateway cannot authenticate to. A backing server registered with a registry-level credential (auth_scheme other than none), or one in the healthy-auth-expired state, no longer appears in a virtual server unless it uses egress authentication. The virtual path never sent that credential, so these servers listed tools that failed when called. The registry logs Skipping virtual backend <path>: it needs a credential the virtual server cannot send for each one. (#2086)
  • A larger shared dictionary for the virtual router. lua_shared_dict virtual_server_map grows from 2 MB to 32 MB in the nginx templates of the registry image. (#2086)
  • Optional: TOOL_REFRESH_ENABLED makes virtual server connects fastest. With it on, a virtual server answers tools/list for each backing server from the tool list the registry stores, after checking the caller's grant, and sends nothing to the backend. The setting is off by default and has a cost: every registry replica then fetches tools from every healthy server once per refresh period, and each list that changed is saved and re-embedded for search. Weigh that load before you turn it on. With it off, the router still asks each backend in turn, and the other changes in this release still apply. See tool list refresh and How a Virtual Server Answers Discovery. (#2086)

New Environment Variables

No new environment variables in this release.

Upgrade Instructions

Deploy the 1.38.1 images for the registry, auth-server and mcpgw.

Docker Compose

cd mcp-gateway-registry
git pull origin main
git checkout 1.38.1

./build_and_run.sh

Kubernetes / Helm (EKS)

cd mcp-gateway-registry
git pull origin main
git checkout 1.38.1

# REQUIRED: the image tags in the subcharts changed, so rebuild the packaged dependencies
cd charts/mcp-gateway-registry-stack
helm dependency build
helm dependency update

# Update values.yaml if needed, then upgrade:
helm upgrade mcp-gateway . -f your-values.yaml

Terraform / ECS

cd mcp-gateway-registry
git pull origin main
git checkout 1.38.1

cd terraform/aws-ecs
terraform plan
terraform apply

Major Features

Faster virtual server discovery

A virtual server used to ask each backing server for its list one after another on every connect, so a server with ten or more internet backends took about 5 to 9 seconds to answer, and Claude could show no tools until a refresh. A test virtual server with 14 internet backends took 8.9 seconds for its first tools/list in Claude Cowork. With this release it leaves out the 4 backends that rejected the gateway's credentials, and the first tools/list for the remaining 10 takes about 0.3 seconds. resources/list dropped from 5.3 seconds to about 1.

  • With TOOL_REFRESH_ENABLED=true, tools/list answers each non-egress backing server from the stored tool list after the grant check. Egress backends and the bundled registry tools server are still asked live, because their list depends on the caller.
  • The router keeps each backing server's list for 60 seconds per user and checks the caller's grant on every use. A backing server whose fetch failed is skipped for 10 seconds, so one failing backend no longer turns off caching for the whole server.
  • resources/list, resources/templates/list and resources/read go only to backing servers with a mapped MCP App tool.
  • Mapping files are written as compact JSON.

PR #2086


What's New

Registry, health and discovery

  • A virtual server answers tools/list, prompts/list, resources/list and resources/templates/list with an empty list when every backing server denies the caller, instead of HTTP 403. A backing server that failed still makes the list an error, and tools/call, prompts/get and resources/read keep their denial. (#2086)
  • The health check reports healthy-auth-expired for a server that answers 401 or 403. (#2086)

Documentation

  • Virtual server operations gains a section on how a virtual server answers discovery, and tool list refresh, MCP Apps and the parameter reference describe the new behavior. (#2086)

Bug Fixes

  • Claude showed no tools on the first connect to a virtual server whose backends were slow to list, or when every backend denied prompts/list. (#2086)
  • A virtual server listed tools from backing servers that rejected the gateway's credentials, and every call to those tools failed. (#2086)

Thanks to Atharva Shirode for the detailed report and request timings in #2079.


Closed Issues

Issue Title Closed By
#2079 Virtual server: first connect fails when list discovery is slow, or when every backend denies prompts/list (HTTP 403) PR #2086
#167 Revert temporary health check status workaround after credentials manager implementation PR #2086

Pull Requests Included

PR Title
#2086 fix(virtual): fast list discovery and empty lists for denied callers

Contributors

Thank you to all contributors for this release:


Support


Full Changelog: 1.38.0...1.38.1

Don't miss a new mcp-gateway-registry release

NewReleases is sending notifications on new releases.