Is the com.googleapis.composer/mcp MCP server working?

Is the com.googleapis.composer/mcp MCP server working?

No, not as the registry describes it. 1 declared endpoint failed the MCP initialize handshake on 2026-09-15 — the protocol's own way of asking a server to identify itself. No tool was ever called.

ERR-2026-1480

Where is the com.googleapis.composer/mcp OpenAPI specification?

Not where the directory says. The URL published as this provider's own document did not answer on 2026-09-15 (34 entries). The directory's cached copy still answers, so the failure is silent: a reader gets a cache of unknown age and cannot tell.

ERR-2026-0400, ERR-2026-0401, ERR-2026-0402, ERR-2026-0403, ERR-2026-0404, ERR-2026-0405, ERR-2026-0406, ERR-2026-0408, ERR-2026-0409, ERR-2026-0411, ERR-2026-0412, ERR-2026-0413

Why can't I reach the com.googleapis.composer/mcp API?

Its declared address answered neither a request nor a TLS handshake on 2026-09-15, across 8 cases. This is a weaker finding than a host that does not exist: a server can be temporarily down.

ERR-2026-0407, ERR-2026-0415, ERR-2026-0416, ERR-2026-0417, ERR-2026-0427, ERR-2026-0432, ERR-2026-0433, ERR-2026-2303

Every record behind those answers

43 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 121 have been across the whole registry.

the description document is gone (34)

The document APIs.guru names as this provider's own origin returns HTTP 404.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://accesscontextmanager.googleapis.com/$discovery/rest?version=v1beta

server error (5)

The declared provider origin answered with a server error.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://apigeeregistry.googleapis.com/$discovery/rest?version=v1

the document refuses machine access (3)

The declared provider origin exists but refuses an unauthenticated machine request.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://cloudprivatecatalog.googleapis.com/$discovery/rest?version=v1beta1

the endpoint is gone (1)

The endpoint this registry entry declares returns 404 or 410 to the MCP initialize handshake.

Check it yourself:

curl -s -X POST https://composer.googleapis.com/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"check","version":"1"}}}'

Withdrawn (1)

Our own check stopped supporting these claims — including claims that were wrong the day they were written.

Also filed as: com.googleapis.composer, googleapis.com, googleapis.com:accesscontextmanager, googleapis.com:acmedns, googleapis.com:adexchangebuyer, googleapis.com:adsense, googleapis.com:adsensehost, googleapis.com:analytics. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.

If a record here is wrong

Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 121 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.

What this page does not tell you

This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.

What this is

A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.

The whole registry, machine-readable: errata.json. Index of subjects: index.html.

Built from registry errata-2026-09-10@b7cb54d3a847. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.