{
  "entry": {
    "kind": "webmcp",
    "slug": "webmcp-bridge",
    "name": "WebMCP Bridge",
    "vendor": "H3manth",
    "description": "WebMCP Bridge projects tools from a remote MCP server into the browser page API, so an agent driving the page can call server-side MCP tools through the same interface it uses for page-declared ones. It stitches the two halves of the ecosystem — hosted MCP servers and in-page WebMCP tools — into a single tool list.\n\nThat convenience is also a trust boundary being erased. Tools that used to require a configured MCP client, with whatever approval flow that client imposes, become callable from a web page. The bridge declares browser control and outbound network access. Anyone deploying it should be explicit about which remote servers are bridged and to which origins, because a page that can reach a filesystem or shell MCP server through a bridge has effectively been granted those capabilities.",
    "website": "https://github.com/h3manth/webmcp-bridge",
    "repository": "https://github.com/h3manth/webmcp-bridge",
    "documentationUrl": null,
    "license": null,
    "version": null,
    "trustLevel": "community",
    "capabilities": [
      "browser:control",
      "network:outbound"
    ],
    "packaging": null,
    "configFiles": null,
    "category": "bridge",
    "updatedAt": "2026-09-02",
    "risk": {
      "score": 40,
      "band": "medium",
      "signals": [
        {
          "id": "trust-community",
          "kind": "trust",
          "label": "Established community project",
          "contribution": -10
        }
      ],
      "dangerousCombos": []
    },
    "dangerousCombos": []
  }
}