The Network Catalog (webGCP)

org.webgcpPublished by webgcp.orgv0.1.0Updated Oct 24, 2026

Semantic search over The Network catalog (skills, agencies, roles) with signed webGCP provenance.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Lets an assistant run semantic searches over The Network catalog of skills, agencies, and roles, with signed webGCP provenance.

What you can do
This remote MCP server exposes semantic search over The Network catalog, covering entries such as skills, agencies, and roles. Results are described as carrying signed webGCP provenance, so an assistant can retrieve catalog matches and present their origin. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth adding when an assistant needs to look up skills, agencies, or roles from The Network catalog and provenance of the results matters. Not useful if you do not work with that catalog.
Requirements
A remote streamable HTTP endpoint at the provider's address; no packages, environment variables, or headers are declared. The manifest declares no authentication, and network access to the endpoint is required.
Before you install
The manifest declares no authentication, so anyone able to reach the endpoint may query it; consider whether the catalog data is sensitive. No credentials, payments, or write actions are shown in the input.

Installation

In SourceWeft

  1. Open The Network Catalog (webGCP) 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/org.webgcp%2Fcatalog/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": {
    "the-network-catalog-webgcp": {
      "type": "http",
      "url": "https://catalog.myparallel.dev/mcp"
    }
  }
}

Tools

2

read_surface

Read an external web surface, discovery-first: returns its WebMCP/MCP server-card manifest when one exists; otherwise DOM-dehydrates the page into an indexed interactive-element text map (static parse, truth_class=inferred).

Parametersurlrequiredmax_chars

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% 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
  • 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.