Skip to content

WebMCP surface / Read the declaration

Every declared tool
opens a question.

Capture the tools your WebMCP page declares, then submit their descriptions, schemas and annotations for assessment. The input and report below use the existing surface-analysis workflow.

Reading a declaration does not execute a tool. The illustration is a metaphor for inspection, rather than a live tool session.

WebMCP · Surface scan

Scan your WebMCP tool surface.

If your product exposes tools to AI agents via WebMCP (document.modelContext), MCP Sentinel can scan what that surface declares - tool descriptions, parameter schemas, annotations, and any resources, prompts or roots you expose - with the real deterministic engine. No fetch, no socket, nothing executed. A surface scan is not listed in the public registry.

Scan in one click

Drag this to your bookmarks bar once. Then, on your own WebMCP page, click it - it reads your tool surface (getTools() or listTools() on document.modelContext or navigator.modelContext, whichever your build exposes), submits it to the scanner, and opens your scored report in a new tab. Same-origin rules mean the read must run on your page, so that single click is all it takes.

Scan my WebMCP page← drag me to your bookmarks bar (one-time)
Or copy the bookmarklet source

Create a new bookmark and paste this as its URL. When you click it on your page it reads your declared tools and submits them to MCP Sentinel's scanner (a surface scan, not listed in the public registry), then opens the report - nothing else on your page is touched.

Or paste your tools manually

The declared surface is analyzed as pasted - no fetch, no socket, nothing is executed. A surface scan is not listed in the public registry.

Runs the real engine over the declared surface. Rate-limited (5 / hour); can take up to ~60s.

02 / Follow the declared evidence

Read what is stated.
Name what is missing.

A surface assessment can inspect description, schema, annotation and protocol evidence. Source, dependency and runtime checks need inputs this declaration does not provide.

The report keeps that coverage boundary visible. Submitted surface metadata is analysed without connecting to the original target, and the surface scan is not published as a registry listing.

A declared surface cannot establish what a tool actually does at runtime.

Assess a published artifact or configuration

Keep the claim attached

A declaration is a starting point.

Read a finding through its evidence and verification steps. Keep the distinction between a declared capability and observed behavior in view.

Explore traceable findings