inboxguard.io WebMCP audit

Rescan
audited Aug 28, 2026in 6s
51/ 100

One tool registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use71
Usefulness50
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
scan_domain: fail

scan_domain

Run a free email-deliverability scan (SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, DNS blocklists) for a domain and return a 0-100 score with per-check findings. Anonymous, no account required, rate-limited to 5 scans/hour per IP.Answers a question. Declared read only.
pagehttps://inboxguard.io/
implementation
viaimperative
entry pointnavigator
registered after235ms
executepresent
api surface
domainrequired
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldtrue
untrusted contentnot declared
titlenot declared
4 findings
passRegistration timing
4 / 4
Every measured tool registered within 235.20000004768372ms of navigation.
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (scan_domain).
fix
{ name: "scan_domain" /* short, unique, verb-based */ }
warningHuman parity
0 / 8
1 of 1 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
scan_domain
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="scan_domain" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "scan_domain",
  "description": "Run a free email-deliverability scan (SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, DNS blocklists) for a domain and return a 0-100 score with per-check findings. Anonymous, no account required, rate-limited to 5 scans/hour per IP.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "domain": {
        "type": "string",
        "description": "Domain to scan, e.g. example.com (apex domain, no scheme or path)."
      }
    },
    "required": [
      "domain"
    ]
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true
  }
}
Showing scan_domain

Findings

WebMCP use

71 / 100 · weight 50
passTools registered
4 / 4
1 tool registered across 1 page.
failReal-browser eligible
0 / 8
The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither.
passRegistration timing
4 / 4
Every measured tool registered within 235.20000004768372ms of navigation.
toolscan_domain
failCanonical entry point
0 / 4
Every tool registers through the deprecated navigator.modelContext alias; move them to document.modelContext before the alias is removed.
toolscan_domain
fix
// Use the canonical entry point - navigator.modelContext is deprecated.
document.modelContext.provideContext({ tools: [/* ... */] });
passSchema validity
5 / 5
All 1 tool declare a structurally valid object input schema.
passSchema quality
4 / 4
All 1 tool schema describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
The one registered tool declares an execute handler.
passAnnotations present
4 / 4
All 1 tool declares a readOnlyHint, so an agent knows which calls change state.
passAnnotation mismatch
3 / 3
No tool claims to be read-only while its name says it writes (1 declared hint checked).
not applicableUntrusted content hint
0 / 2
No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
1 tool was registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.
fix
document.modelContext.dispatchEvent(new Event("toolchange"));
not applicableInjection surface
0 / 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

50 / 100 · weight 30
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 1 name does not start with a verb (scan_domain).
toolscan_domain
fix
{ name: "scan_domain" /* short, unique, verb-based */ }
not applicableDescription quality
0 / 6
The description-quality model hop returned no usable result, so descriptions were not rated.
not applicableTool selection
0 / 14
The tool-selection model hop returned no usable result.
not applicableCoverage vs. site type
0 / 8
This tool set does not place the site in a category with a known expected tool shape, so there is no coverage baseline to score it against.

Human experience

0 / 100 · weight 20
warningHuman parity
0 / 8
1 of 1 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
toolscan_domain
scan_domain
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="scan_domain" tooldescription="...">
  <!-- the same action, as UI -->
</form>
not applicablePage experience
0 / 12
The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.
how this was captured
chrome
148.0.7778.96
capture shim
v1
spec snapshot
2026-08
mode
fast
pages
1
tools
1
run time
6s
finished
Aug 28, 2026