Deploy applications to Cloud Run
Inferido de los transportes que declara este listado (streamable-http). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.
La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.
Leído de un handshake MCP real initialize → tools/list contra el endpoint declarado. No se invocó ninguna herramienta: tools/list es la llamada de introspección de solo lectura que el protocolo define para esto. Refleja lo que el servidor anunciaba en ese momento; un endpoint alojado no está fijado a ninguna versión y puede cambiar sin avisar.
https://run.googleapis.com/mcp5 herramientas · 851 msget_serviceGet info about a Cloud Run service, such as its URI and whether the deploy succeeded.Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.
No se publicó ningún esquema de entrada para esta herramienta.
list_servicesList Cloud Run services in a given Google Cloud project and region.List Cloud Run services in a given Google Cloud project and region.
No se publicó ningún esquema de entrada para esta herramienta.
deploy_service_from_imageDeploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.
No se publicó ningún esquema de entrada para esta herramienta.
deploy_service_from_archiveDeploy 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).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).
No se publicó ningún esquema de entrada para esta herramienta.
deploy_service_from_file_contentsDeploys 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.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.
No se publicó ningún esquema de entrada para esta herramienta.
5 de 5 herramientas publicaron una descripción.
Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.
Deploy applications to Cloud Run
Los nombres enlazados abren el índice de Forge con todas las entradas que se observó que exponen esa herramienta. Ver todas las herramientas indexadas.
Esta entrada no publica ningún paquete de npm, así que Forge no tiene un árbol de dependencias para ella. Es una carencia de cobertura, no una afirmación de que no tenga dependencias.