WebMCP Directory

What this directory is

The WebMCP Directory is a voluntary, evidence-led catalogue of websites whose owners want to make their agent-facing capabilities discoverable. It is not a search index of every website and it does not scrape or republish a site’s content. The directory starts empty by design: an empty or thin generated list should not be indexed as if it were a useful collection.

What “Verified” means

Verified means that the submitter completed an ownership check for the listed domain and that BTradeTech reviewed the submitted public URL on a stated date. The review can record detected WebMCP signals, candidate actions, read-only versus action mix and a temporary report link. It does not mean that every tool is safe, that every browser supports it, that the website is legally compliant, or that an agent can complete a transaction without human involvement.

Verification criteria

1. The URL must be a public HTTPS origin without embedded credentials.
2. The submitter must demonstrate control of the domain through the verification method provided after submission.
3. The public page must be reachable and substantial enough to describe a real user workflow; empty reports and temporary scans are excluded.
4. Static evidence and any controlled runtime evidence must be dated and labelled separately.
5. Consequential actions must remain clearly confirmation-required, and the listing must not imply that the directory bypasses authentication, consent or authorization.

What a listing can show

A reviewed entry may show the domain, category, review date, detected tool count, action categories, evidence status and a link to a noindex report. Status labels matter: Detected means the page contains evidence of a useful workflow; Suggested means a tool is an implementation opportunity; Runtime verified requires a real controlled-browser test. Pending ownership is never shown as Verified.

How to submit responsibly

Submit the canonical public URL, a useful category and an email that can complete ownership verification. Do not submit private staging URLs, credentials, customer data or a claim that the site supports a browser or action that has not been tested. Owners can request correction or removal of their listing. The directory records participation; it is not an endorsement, security audit or certification.

Use the directory with the WebMCP tools

Before requesting a listing, run the Checker for static evidence, use the Simulator for a concrete task, and prioritise work with Autopilot. The Generator can produce a reviewable scaffold, while the Validator helps review the implementation. For production work, see the Implementation Service.

Evidence lifecycle and removal

Directory evidence is time-bound. A verified entry should be reviewed again when the site changes its domain, authentication flow, framework, forms or WebMCP registration. If the owner can no longer verify control, the listing becomes pending or is removed. This prevents an old scan from being presented as a current capability and keeps the empty-directory state honest until there are real, owned entries.

What visitors should check

Visitors should inspect the review date, action status, risk category and whether runtime was actually tested. A read-only result may still expose private account data and needs authorization. A suggested quote, booking or checkout action is a planning lead, not a commitment. Use the listing to decide what to test next, then confirm behavior on the target website and with the website owner.

Why evidence quality matters

A directory entry is useful only when a visitor can understand what was checked and what remains unknown. A URL, a tool count and a green label are not enough: the page should identify the reviewed origin, the date, the action category and whether a browser actually executed the workflow. This makes the directory a practical starting point for evaluation instead of a badge marketplace.