A practical guide to RealCryptoCap's WebMCP compatibility: how browser-based AI agents discover read-only market tools, search the native-crypto index, and open the right pages without guessing at the interface.
RealCryptoCap now supports WebMCP so compatible browser-based AI agents can connect directly to the site through explicit, structured tools instead of relying only on visual page interpretation.
WebMCP is a browser-side bridge built around the Model Context Protocol. A participating website registers tools with names, descriptions, input schemas, and functions. An AI client can discover those tools and ask the page to perform a defined, user-visible task.
RealCryptoCap exposes read-only tools for the native-crypto index overview, public market search, and safe navigation to site pages. A separate WebMCP tool connects the agent to RealCryptoCap AI analysis through the public/free AI path, so an agent can ask a crypto or website question and receive the site assistant's response.
The index tool is useful because RealCryptoCap is not simply a mirror of every reported crypto-market-cap list. The site removes stablecoins, wrapped and staked receipt assets, tokenized securities and funds, commodity representations, and other non-native or duplicate products from the core native-crypto ranking.
The search workflow gives an agent a structured result rather than forcing it to infer a row from a visual table. The agent can locate a symbol or name, summarize returned market fields, and link the user to the relevant coin page for inspection.
The RealCryptoCap AI connection is deliberately separated from Pro context. The WebMCP AI tool sends the question with the free-mode flag and no Market Data, API, CLI, or MCP context. Pro-only navigation and data remain gated for logged-in Pro subscribers.
WebMCP does not grant an agent permission to trade, withdraw funds, change an account, or bypass authentication. The RealCryptoCap tools are designed for research and navigation, while exchange actions and execution remain outside the website tools.
A typical interaction looks like this: ask an AI assistant for the current RealCryptoCap native-asset overview; let it call the index tool; ask it to find a coin; connect to RealCryptoCap AI analysis for a plain-language question; then open the relevant public page for review.
Connect a client: WebMCP uses a small local MCP bridge. For Claude Desktop, add a webmcp server entry to the client configuration: { "mcpServers": { "webmcp": { "command": "npx", "args": ["-y", "@jason.today/webmcp@latest", "--mcp"] } } }. Restart Claude Desktop if it does not discover newly registered tools.
OpenClaw can use the same stdio MCP bridge when MCP support is enabled. A typical setup is `openclaw mcp add webmcp --command npx --arg -y --arg @jason.today/webmcp@latest --arg --mcp`, followed by `openclaw mcp doctor --probe` or the equivalent tool-list check for your installed version.
Hermes can add the bridge in `~/.hermes/config.yaml` under `mcp_servers`: `webmcp: { command: npx, args: ["-y", "@jason.today/webmcp@latest", "--mcp"] }`. Start Hermes, then confirm that the webmcp server and its tools are available. If your client uses a different MCP config path, follow that client's current MCP documentation.
After the local bridge is running, ask the MCP client to create a WebMCP registration token, open the WebMCP widget on RealCryptoCap, and paste the token into the widget. The token is single-use for registration; the website receives its own session connection. Official references: https://webmcp.dev/ and https://github.com/jasonjmcghee/WebMCP.
Once connected, ask the agent to list its RealCryptoCap tools. It can then call the public index/search tools, open allowed pages, and connect to RealCryptoCap AI analysis. Non-Pro sessions are not given Pro Market Data, API, CLI, or MCP context.
For developers, the browser bridge is loaded as a small public script and the site registers tools immediately after initialization. Tool descriptions are specific, inputs are schema-defined, outputs are concise, and no destructive actions are exposed.
The WebMCP widget is optional. Users can browse RealCryptoCap normally, while compatible AI clients can connect through their own WebMCP/MCP workflow. Availability depends on the client, browser, and bridge connection.