Google Cloud 17,671 API, SKU & MCP Schema Catalog

io.ceadigitalPublished by ceadigital.ioOfficial publisherv1.0.0Updated Nov 5, 2026

Sub-millisecond FTS5 search across 17,671 Google Cloud APIs, SDKs, Billing SKUs, and MCPs.

The publisher's own server: CEA Digital B2A Fulfillment Factory

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server with fast full-text search over a Google Cloud API, SKU and MCP catalog, plus knowledge, CVE and package-health lookups.

What you can do
  • Search a catalog of 17,671 Google Cloud, Vertex AI and A2A service records, including APIs, SDKs, billing SKUs and MCPs
  • Search video transcript chunks and knowledge graph triples in a local vault database
  • Audit package vulnerabilities and CVE advisories against the OSV.dev database
  • Inspect package health across the NPM and PyPI ecosystems in parallel
When to use it
Useful when an assistant needs to look up Google Cloud services, SKUs or MCP schemas, check whether a dependency has known vulnerabilities, or compare package health before adding a library.
Requirements
A remote streamable HTTP endpoint; no package installation, environment variables or headers are declared. No authentication is declared.
Before you install
The vulnerability and package-health tools query third-party sources (OSV.dev, NPM, PyPI), so package names you submit leave the session. Results are advisory; verify findings before acting on them.

Installation

In SourceWeft

  1. Open Google Cloud 17,671 API, SKU & MCP Schema Catalog in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.ceadigital%2Fgcp-cloud-catalog-search/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "google-cloud-17-671-api-sku-schema-catal": {
      "type": "http",
      "url": "https://ceadigital.io/mcp/gcp-catalog"
    }
  }
}

Tools

4

security_cve_audit

Audit package vulnerabilities and CVE advisories via OSV.dev database.

Parameterspackagerequiredversionecosystem

package_health_pulse

Parallel health pulse inspection across NPM and PyPI ecosystems.

Parameterspackage_namerequired

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Ceadigital integrations