Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google Cloud Run

REMOTE · RUN.GOOGLEAPIS.COM · SCANNED SEP 20

Deploy applications to Cloud Run

0 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 628 tokens (~125/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Google Cloud Run MCP server?

Google Cloud Run is a hosted endpoint at https://run.googleapis.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · run.googleapis.com

# add to Claude Code
claude mcp add --transport http com-googleapis-run-mcp 'https://run.googleapis.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-googleapis-run-mcp": {
      "url": "https://run.googleapis.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-googleapis-run-mcp": {
      "type": "http",
      "url": "https://run.googleapis.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-googleapis-run-mcp]
url = "https://run.googleapis.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-googleapis-run-mcp": {
      "type": "remote",
      "url": "https://run.googleapis.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-googleapis-run-mcp --url 'https://run.googleapis.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-googleapis-run-mcp:
    url: "https://run.googleapis.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-googleapis-run-mcp": {
      "Transport": "http",
      "Url": "https://run.googleapis.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-googleapis-run-mcp -t streamable-http -u 'https://run.googleapis.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-googleapis-run-mcp": {
      "type": "http",
      "url": "https://run.googleapis.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://run.googleapis.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=upload.video.google.com CN=WR2,O=Google Trust Services,C=US 4 Sept 2026 27 Nov 2026 ECDSA 256 SHA256-RSA 26b7552c6ebf922f0aa0ebf2fb6115e4
SANs: upload.video.google.com, *.clients.google.com, *.docs.google.com, *.drive.google.com, *.gdata.youtube.com, *.googleapis.com, *.photos.google.com, *.youtube-3rd-party.com, upload.google.com, *.upload.google.com, upload.youtube.com, *.upload.youtube.com and 5 more
CN=WR2,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a07c4cded100ad9d66a5107b98
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of run.googleapis.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
googleapis.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://run.googleapis.com/mcp Verified 200
http (plaintext) http://run.googleapis.com/mcp Inconclusive 405
MCP tools · 5 exposed · ~628 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
deploy_service_from_archive ~309

Deploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the container image build step for faster deployment. The archive must include all dependencies: - For compiled languages (Go, Java), include pre-compiled binaries. - For scripting languages (Python, Node.js), include pre-installed libraries (e.g., vendor/, node_modules/). Deployment steps: 1. Package source code and dependencies into a .tar.gz archive (max 250MiB). It's recommended to create archive from the root of the application's source directory. 2. Upload the archive to a Google Cloud Storage bucket, preferably in the same region as the service. 3. Deploy to Cloud Run using this tool, specifying: - source_code: Google Cloud Storage object path to the archive (e.g., gs://bucket/object). - command: Command to start the application. - base_image_uri: Base image for the container (e.g., go124, nodejs24, python314). See https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images for options. The runtime picked should match the local environment. - args: (Optional) Arguments for the command. - env: (Optional) Environment variables (e.g., name: `PYTHONPATH`, value: `./vendor`). - ports: (Optional) Container ports to expose (defaults to 8080).

NameTypeReqDescription
serviceyesRequired. The service to deploy.
NameTypeReqDescription
donebooleanIf the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
errorThe error result of the operation in case of failure or cancellation.
metadataobjectService-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method…
namestringThe server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{u…
responseobjectThe normal, successful response of the operation. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get…

No examples provided.

deploy_service_from_file_contents ~148

Deploys a Cloud Run service directly from local source files. This method is suitable for scripting languages like Python and Node.js, of which the source code can be embedded in the request. This is ideal for quick tests and development feedback loops. You must include all necessary dependencies within the source files because it skips the build step for faster deployment. **Key Requirements:** 1. source_code: Should set to sourceCode.inlinedSource.sources with array of source files, each having `filename` and `content`. 2. Size limit: you are subject to total request size limit of 50MiB.

NameTypeReqDescription
serviceyesRequired. The service to deploy.
NameTypeReqDescription
donebooleanIf the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
errorThe error result of the operation in case of failure or cancellation.
metadataobjectService-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method…
namestringThe server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{u…
responseobjectThe normal, successful response of the operation. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get…

No examples provided.

deploy_service_from_image ~37

Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.

NameTypeReqDescription
serviceyesRequired. The service to deploy.
NameTypeReqDescription
donebooleanIf the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
errorThe error result of the operation in case of failure or cancellation.
metadataobjectService-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method…
namestringThe server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{u…
responseobjectThe normal, successful response of the operation. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get…

No examples provided.

get_service ~77

Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.

NameTypeReqDescription
namestringyesRequired. The short name of the Service.
projectstringyesRequired. The project ID or project number to get the Service from.
regionstringyesRequired. The region to get the Service from.
NameTypeReqDescription
createTimestringThe creation time.
creatorstringEmail address of the creator.
lastModifierstringEmail address of the last modifier.
namestringThe fully qualified name of this Service. Format: projects/{project}/locations/{location}/services/{service_id}
templateThe template used to create revisions for this Service.
terminalConditionThe terminal condition of this Service, indicating its readiness status. State CONDITION_SUCCEEDED means the service is ready. If the service is not ready, this condition will contain detailed error…
updateTimestringThe last-modified time.
uristringThe main URI in which this Service is serving traffic.

No examples provided.

list_services ~57

List Cloud Run services in a given Google Cloud project and region.

NameTypeReqDescription
projectstringyesRequired. The project ID or project number to list the Services from.
regionstringyesRequired. The region to list the Services from.
NameTypeReqDescription
projectstringThe project where the Services are listed from.
servicesarrayThe resulting list of Services.

No examples provided.

Common questions

What is the Google Cloud Run MCP server?

Google Cloud Run is an MCP server listed in the public MCP registry as com.googleapis.run/mcp. Deploy applications to Cloud Run. This page covers its hosted endpoint (https://run.googleapis.com/mcp).

Is the Google Cloud Run MCP server safe to use?

Google Cloud Run scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Google Cloud Run MCP server expose?

Google Cloud Run exposes 5 tools: get_service, list_services, deploy_service_from_image, deploy_service_from_archive, deploy_service_from_file_contents. Their descriptions and schemas cost roughly 628 tokens of context every time the server is loaded.

Does the Google Cloud Run MCP server require authentication?

No. We connected to Google Cloud Run without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Google Cloud Run MCP server still maintained?

Google Cloud Run is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.