HUMΛN
Ask HUMΛN

Ask how HUMΛN governs an agent.

No account is required and no identity is collected. The question and the page path are logged with the session so answers can be reviewed. The deployment credential stays on the server. Sessions expire with the public Q&A contract.

← Community Developer

WebMCP vs org MCP — two products, one trust story

2026-08-03 HUMΛN Team Developer 10 min

Org mesh MCP exposes your platform to AI clients. WebMCP governs browser tools on the open web. Confuse them and you ship the wrong threat model.

If you remember one diagram from HUMΛN’s MCP story, make it this:

Org MCP WebMCP trust layer
Where https://{org}.mcp.haio.run Browser window.webmcp + HUMΛN bridge
Who calls Cursor, Claude Desktop, IDE agents Pages and extensions on the open web
What you expose Your workflows, agents, catalog Site tools inbound/outbound under HumanOS
Threat focus Delegation abuse inside the org mesh Origin, approval, data minimization on arbitrary sites

Same company. Same taste for receipts. Different products.

The hook: the wrong README

A team reads “MCP” once, wires the org endpoint into a browser experiment, and wonders why origin scoping and external adapters feel bolted on. Or they expect {org}.mcp.haio.run to wrap every website tool on earth. Both mistakes come from collapsing two nouns into one acronym.

Org MCP in one sentence

Your org as an MCP server — governed colleague to the platform you already run. See Your org is an MCP server.

WebMCP in one sentence

A browser trust layer for WebMCP tools: facade (expose HUMΛN capabilities) and adapter (discover/govern external site tools), both through identity, delegation, approval, capability routing, minimization, and provenance.

Transport essays (Streamable HTTP) explain how bytes move. This essay explains which product you meant.

So that buyers and builders pick deliberately

Say “org MCP” when you mean AI clients calling your mesh. Say “WebMCP” when you mean browser tool governance. If a deck mixes them, send them this table before the pilot starts.

Scroll-stopper: One word — MCP — two threat models. Pick the noun before you pick the URL.

Try it on this site

This page is not a brochure. builtwithhuman.com dual-registers seven Answer-only WebMCP tools so a co-browsing agent can find docs and explain pillars without scraping the hero.

Surface How to inspect
HUMΛN bridge window.webmcp.tools — same list discoverWebMCPTools reads
Chrome / W3C await document.modelContext.getTools()

Tools: search_site, get_doc, list_guides, get_developer_path, list_pillars, explain_pillar, get_current_page. v1 is Answer only — no navigation, no purchases. Catalog: /ai/webmcp-catalog.json. Append ?webmcp_debug=1 for a console trail.

Bridge setup (MV3): monorepo docs/webmcp/extension-setup.md. Machine article: /ai/articles/site-webmcp-answer-tools.md.

Operator follow-up after production deploy: list builtwithhuman.com on webmcp.com (directory presence is ops, not a code gate).

Go deeper