Skip to content
MCPSTAMP
MCP server report

Mcp MCP server

com.googleapis.compute/mcp

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 91 of 100 (grade A), higher than 62.2% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, Gemini and MCP Registry. Not ready for ChatGPT.

Measured facts

Score
91A
Sign-in
OAuth
Tools listed
29
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Not ready Blocked by issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT).
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

4 checks to fix

  1. Fails

    issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT)

    auth_chatgpt_metadata

    Blocks ChatGPT.

    Measured issuer "https://accounts.google.com" is not exactly the authorization_servers entry "https://accounts.google.com/"

    Use the exact metadata "issuer" string in the protected resource metadata authorization_servers list (no trailing-slash or case differences), and list token_endpoint_auth_methods_supported (for example ["none"] for public clients) in the au

  2. Fails

    Server instructions

    instructions

    Measured No instructions in the initialize result

    Add an "instructions" string to the initialize result: what the server covers, for whom, and its limits.

  3. Warning

    Client registration (DCR or Client ID Metadata Documents)

    auth_registration

    Measured No registration_endpoint and no client_id_metadata_document_supported

    Add a Dynamic Client Registration endpoint (RFC 7591) or set client_id_metadata_document_supported: true; otherwise every store needs a manually issued client id.

  4. Warning

    initialize latency

    latency

    Measured 1820 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

22 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, serverInfo name and version, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, PKCE S256 advertised, refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool, Tool descriptions.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Mcp

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcompute.googleapis.com%2Fmcp)](https://www.mcpstamp.com/r/com-googleapis-compute-mcp/)

HTML

<a href="https://www.mcpstamp.com/r/com-googleapis-compute-mcp/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcompute.googleapis.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
Registry name
com.googleapis.compute/mcp
Remote URL
https://compute.googleapis.com/mcp
Version
1.0.0
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026