AWS has put its managed MCP server closer to the developers using it. In The AWS MCP Server is now available in six additional AWS Regions, the release names Singapore, Sydney, Tokyo, Ireland, London and Oregon, joining North Virginia and Frankfurt for eight in total. The server, part of the Agent Toolkit for AWS, “gives AI coding agents a single interface to AWS APIs, so agents can discover and call AWS services without building and maintaining per-service integrations.” The reason given is plain: lower latency, and the ability to “keep request data within the Region to meet data residency requirements.”
There are no figures beyond the region count, and the one distinction worth keeping is in the last sentence of the body. “The AWS MCP Server can access services in all commercial AWS Regions, while the AWS MCP Server itself runs in the Regions listed below.” Where the server runs and where it can act are separate facts. A team in London can point its coding agent at a London endpoint so the request stays in the region, and the agent can still provision infrastructure anywhere the account allows. That is the right design for residency, and it means the governance question is the caller’s credentials, not the endpoint’s location.
The catalog has a finding to report against the release, and it is partly about us. The Amazon Web Services provider page lists 1,685 API pages, and the agentic access profile maps 5,181 operations, 3,518 of them acting and 147 human-in-the-loop, the largest acting surface the catalog holds. On the Agent Readiness score, spec presence, agentic access, reversibility, auth clarity, the rate limit signal and delegated identity are lit. The MCP server dimension is unlit. Last week this series covered Amazon SES shipping agent skills for this same server, and the SES record lights it. The server that eight regions now host is not credited to the record of the company that runs it.
The Kin Score is 59.4, strong band, with access clarity at 100.0 and developer ergonomics at 64.3 against contract quality at 26.3. The Agent Readiness score is 30.5, agent-ready. This is the same seam roadmap issue #958 describes for Google Cloud and BigQuery, from the other direction: there, a product record missed its parent’s server, and here the parent misses a server one of its products already credits. A probe that looks for an MCP server where a company’s API lives will not find one AWS hosts at a separate endpoint for all of its APIs at once. The release puts the door in eight regions. The catalog still has to learn which record it belongs to.