WebMCP execution verified

Test date: 14 September 2026
Publisher and service operator: WagerX

On the live WagerX Agentic Gambling Index, ask_wagerx_directory was successfully discovered and executed through Chrome’s native WebMCP API, returning WagerX catalog evidence.

Scope: WagerX’s own automated browser verification. Not an independent certification, an independently operating AI agent, or proof of universal browser support. This is a dated observation, not a continuously refreshed health check.

Test environment

• Published page: https://wagerx.io/agentic-gambling-index.
• Google Chrome for Testing 155.0.8057.0, headless, driven by Playwright.
• Native WebMCP enabled with --enable-experimental-web-platform-features. No WebMCP polyfill.
• Tool discovered with document.modelContext.getTools() and invoked with document.modelContext.executeTool(tool, {question}).

Observed results

• Discovery passed: exactly one declarative tool, ask_wagerx_directory.
• Schema passed: the browser generated an object schema containing the required string parameter question.
• Known provider passed: a Crypto.com query returned WagerX’s catalog evidence.
• Unknown provider passed: “Is ahel.io in the directory?” returned not_found, rather than an invented record. This describes that lookup at test time, not a permanent claim about the provider.
• Scope boundary passed: “Which casino has the best bonus?” returned out_of_scope. This directory tool does not make casino-bonus recommendations.
• Response parity passed: native tool output matched the backend response, and its answer matched the text displayed on the page.

Ordinary browsing and compatibility

Chrome 145.0.7632.6 passed normal form submission, JavaScript-disabled form submission, HTTP/network error handling, and mobile control-bound checks.

In the tested Chrome 155 build without the experimental feature flag, document.modelContext was not exposed. No origin-trial token was observed in the live page’s meta tags or response header.

What this does not prove

• It does not establish that an external AI independently discovered, chose or used this tool.
• It does not independently validate every catalog claim, certify listed providers, or establish future endpoint availability.
• It does not establish support in every browser or WebMCP client.
• The tool performs bounded catalog lookups. It does not execute remote MCP tools, place bets, transfer funds or start autonomous missions.
• WebMCP browser execution is separate from WagerX’s server-side MCP and A2A interfaces.

Method and record

The automated native checks used WagerX’s tests/webmcp_directory_browser.py runner against the published origin. The runner’s tool argument was updated from a JSON string to an object for Chrome 155; the site’s WebMCP implementation did not need a change. The accompanying backend/catalog suite passed 31 tests.

This report summarizes the observed test output; it is not a signed browser attestation or an independently timestamped certificate. No exact execution time is asserted.

Implementation reference: Chrome’s WebMCP declarative API documentation.