WebMCPify Search · Launching soon

Search what the web can do.

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.

CAPABILITY SEARCH

Pages describe information.
Capabilities describe action.

LAUNCHING SOON The interface works, but this deployment has no configured capability index or invocation backend yet.

SEARCH INDEX

Start with an intent.

Real capability records will appear here with source attribution, schemas, risk, authentication, freshness and verification signals.

No sample results are shown as real data.

Direct submission

Submit a WebMCP-enabled site

Submission is separate from crawler and sitemap discovery. No URL is fetched from this form, and an unconfigured backend returns an explicit unavailable result.

The complete Search loop

Intent in. Verified capability out.

Search is designed to carry source and health information through discovery, selection and invocation—without turning an execution claim into proof.

  1. 01

    Discover WebMCP-enabled websites.

  2. 02

    Index sites, tools, schemas and descriptions.

  3. 03

    Search by natural-language intent.

  4. 04

    Rank relevant capabilities.

  5. 05

    Inspect authentication, input and risk requirements.

  6. 06

    Invoke a selected tool when supported.

  7. 07

    Verify the outcome.

  8. 08

    Record success, failure, latency and freshness.

WebMCPify Scout · In development

An independent crawler for the actionable web.

Scout is the planned discovery pipeline inside Search: find permitted public WebMCP surfaces, recheck them, and preserve where every record came from.

01

Independent crawl

Discovers public capability signals while respecting robots rules, origin boundaries and crawl limits.

02

Direct submission

Lets publishers request discovery while keeping submitter intent and first-party attribution visible.

03

Publisher feeds

Imports approved first-party records with provenance and freshness attached.

04

Ecosystem submissions

Lets maintainers contribute verifiable site and tool records under their applicable terms.

05

Browser verification

Revisits supported sites to distinguish a directory record from a currently observed runtime tool.

06

No unsupported brands

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

Meet agents where they already work.

Search is being designed as infrastructure, not just a destination page. Each access path keeps source, risk and availability visible.

01

Web preview

People can try the interface, inspect its status, and later open a matched website.

02

Native WebMCP

A compatible browser agent can discover the page-scoped Search tools; backend-dependent calls report unavailable honestly.

03

webmcpify-search

A planned MCP server for IDEs, coding agents, voice agents, and developer applications.

PLANNED
04

WebMCPify Guard

The open-source, user-owned security layer that protects the full action path and can connect MCP-compatible agents to website WebMCP tools.

PLANNED
See the native tools available on this page
search_web_capabilitiesget_capability_detailslist_site_capabilitiesget_capability_healthsubmit_webmcp_siteinvoke_web_capability