Turn real actions into WebMCP tools. Test in Chrome. Track tool health without payloads.
siteverbsiteverb / stateful fixtureRPcatalog.search-products1,814
cart.add-item1,067
cart.get-current793
PR #8 · failed1 journey
PR #7 · passed1 journey
main · currentv0.1.0
e6f85bb1930250090bf18755Understand
WebMCP is a proposed web standard for exposing structured website actions as tools that AI agents can discover and invoke. It replaces brittle click sequences with explicit names, schemas and results.
Read the Chrome overview →Verify
Siteverb audits the declared contract, discovers tools in a named browser and runs deterministic journeys with explicit postconditions before a release can pass.
See the conversion workflow →Measure
Siteverb groups calls, outcomes and bounded latency by stable tool ID. It does not collect prompts, arguments, results, DOM, credentials or user identity.
Review the data boundary →$ npx skills add siteverb/siteverb --skill siteverb✓ WebMCP surface mapped
✓ 6 stable tools declared
✓ 1 journey ready to verify
The Siteverb skill maps real app actions, wires the SDK and writes one reviewable siteverb.webmcp.json contract.
1 passed · 0 failed · 0 skipped
Your GitHub Action runs deterministic journeys in a named browser. Siteverb keeps one release Check current.
See calls, outcomes and latency by stable tool ID—without prompts, arguments, results or DOM.
Calls, outcomes and bounded latency, grouped by the stable ID already in your contract.
Prompts, arguments, results, DOM, identities and raw errors have no field in the event contract.
Failed journeys name the affected stable tool and recent call volume—never a causal claim.
Pull request #28Checkout journey failed
cart.prepare-checkoutaffected tool
New commits replace stale evidence. Duplicate deliveries never create a second Check.
The skill, SDK, contract, audit, runner and Action work without an account. The cloud adds history, not lock-in.
Live staging evidence
Passing and failing pull requests, plus one idempotent SDK batch, meet in the same console.
Deliberate acceptance failureFind a trail shoe and prepare checkout
catalog.search-productsTrust boundary
Registration only exposes a tool. Your server still authorizes every action. Siteverb never becomes an agent or execution plane.
Read the security modelQuestions
No. Your repository’s own GitHub Action runs deterministic browser journeys. Siteverb validates the bounded report and updates one Check.
Stable tool identity, schema hash, release, environment, outcome and duration. Prompts, arguments, results, DOM, credentials, full URLs, user IDs and raw errors are excluded from the event contract.
Siteverb records exactly which stable tool ran. It does not guess whether the caller was ChatGPT, Claude or a specific person because browser callback metadata is not trustworthy identity. Referral traffic and tool invocation are separate signals.
Chrome 152 has a Siteverb real-browser pass. ChatGPT Site Tools and Edge 150 use dated documented profiles. Additional clients are added only when evidence exists.
The GitHub App fails the Siteverb Check and adds the previous seven days of observed calls for affected stable tools as context. It never claims the pull request caused those calls.
Yes. The open skill, SDK, contract, audit, runner and customer-owned Action remain usable without an account or hosted connection.
Not yet. The private alpha is limited to allowlisted staging fixtures until live uninstall, deletion, retention and privacy-policy gates are complete.
Private alpha
Review release evidence and call health in one place.