Privacy Policy

Last updated: February 2025

Overview

WebMCP Hub is an open community registry of WebMCP configurations for AI agents. This policy covers both the WebMCP Hub website (webmcp-hub.com) and the WebMCP Hub Chrome extension.

What the Chrome extension does

The extension registers WebMCP tool definitions on web pages so that AI agents can interact with websites through structured tools instead of screen scraping.

It works by looking up the current page's domain against the WebMCP Hub registry. If a matching configuration exists, the extension registers the defined tools on the page. If no configuration matches, the extension does nothing.

Data collected by the extension

When you navigate to a web page, the extension sends the following to the WebMCP Hub API to check for matching configurations:

  • Domain name of the page you are visiting (e.g. google.com)
  • URL path of the page (e.g. /dashboard/settings)

The extension does not collect or transmit:

  • Page content, form data, or any data you enter on websites
  • Cookies, authentication tokens, or session data
  • Browsing history beyond the current navigation lookup
  • Personal information such as your name, email, or IP address

How data is used

  • Config lookup: Domain and path are used solely to find matching WebMCP configurations. The lookup is stateless — the API does not log or store individual requests.
  • Session cache: Matched configurations are stored temporarily in the browser's session storage (per tab) and are automatically removed when the tab is closed.
  • Hub URL setting: Your configured hub URL is stored in Chrome sync storage so it persists across devices. No other settings are stored.

Data collected by the website

The WebMCP Hub website collects only what is necessary to operate the registry:

  • GitHub account info (username, profile image) if you sign in to contribute configurations
  • Configurations you submit (domain, tools, metadata) which are publicly visible in the registry

Third-party services

  • Vercel — Hosts the website and API
  • Supabase — Database for the configuration registry
  • GitHub OAuth — Authentication for contributors

We do not use analytics, tracking pixels, or advertising services.

Data retention

Configuration data in the registry is retained as long as the registry operates. Contributors can request removal of their submitted configurations at any time. The extension does not persist any browsing data — all lookup data is session-scoped and cleared when the tab closes.

Your choices

  • You can uninstall the extension at any time to stop all lookups
  • You can change the hub URL via the extension popup settings if you want to use an alternative registry
  • You can delete your account and contributed configurations by contacting us

Changes to this policy

We may update this policy as the project evolves. Significant changes will be noted in the extension's changelog. Continued use of the extension or website after changes constitutes acceptance of the updated policy.

Contact

If you have questions about this policy or want to request data removal, reach out via email: email

A public GitHub repository is coming soon — once open-sourced you will also be able to open issues there.