Independent crawl
Discovers public capability signals while respecting robots rules, origin boundaries and crawl limits.
WebMCPify Search · Launching soon
Find WebMCP-enabled sites by the actions they expose, inspect the requirements, then visit the site or invoke the chosen capability through a supported agent path.
Pages describe information.
Capabilities describe action.
LAUNCHING SOON The interface works, but this deployment has no configured capability index or invocation backend yet.
Real capability records will appear here with source attribution, schemas, risk, authentication, freshness and verification signals.
No sample results are shown as real data.The complete Search loop
Search is designed to carry source and health information through discovery, selection and invocation—without turning an execution claim into proof.
Discover WebMCP-enabled websites.
Index sites, tools, schemas and descriptions.
Search by natural-language intent.
Rank relevant capabilities.
Inspect authentication, input and risk requirements.
Invoke a selected tool when supported.
Verify the outcome.
Record success, failure, latency and freshness.
WebMCPify Scout · In development
Scout is the planned discovery pipeline inside Search: find permitted public WebMCP surfaces, recheck them, and preserve where every record came from.
Discovers public capability signals while respecting robots rules, origin boundaries and crawl limits.
Lets publishers request discovery while keeping submitter intent and first-party attribution visible.
Imports approved first-party records with provenance and freshness attached.
Lets maintainers contribute verifiable site and tool records under their applicable terms.
Revisits supported sites to distinguish a directory record from a currently observed runtime tool.
Live examples come from confirmed WebMCP records—not familiar sites that have no known integration.
Every indexed record keeps its source and freshness visible. Directory coverage is never represented as a live guarantee without a separate verification signal.
One search layer · four ways in
Search is being designed as infrastructure, not just a destination page. Each access path keeps source, risk and availability visible.
People can try the interface, inspect its status, and later open a matched website.
A compatible browser agent can discover the page-scoped Search tools; backend-dependent calls report unavailable honestly.
A planned MCP server for IDEs, coding agents, voice agents, and developer applications.
PLANNEDThe open-source, user-owned security layer that protects the full action path and can connect MCP-compatible agents to website WebMCP tools.
PLANNEDsearch_web_capabilitiesget_capability_detailslist_site_capabilitiesget_capability_healthsubmit_webmcp_siteinvoke_web_capability