anew.page WebMCP audit

audited Aug 28, 2026in 4s
59/ 100

6 tools registered. Strongest in WebMCP use, weakest in human experience.

WebMCP use89
Usefulness50
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
anew_write: warning

anew_write

Encode a self-contained HTML document or fragment into a new anew.page URL — a sibling page, independent of the current one. Returns the new URL and its byte counts; does not navigate or mutate the current page — rewriting the page being viewed is anew_edit's job, the tool a viewed page registers alongside this one. Inline all CSS, JS, and images (data: URIs, inline SVG, CSS gradients, or emoji) — the page should render alone forever, and each external reference gambles it on someone else's host staying up. One accepted exception: a webfont is far too large to inline, so a font may load from a durable CDN with a system-stack fallback; do not fight a user who asks for one. The HTML should stay ≤ 160000 UTF-8 bytes and the encoded URL ≤ 4000 bytes — the recommended share-safe budgets, not walls: a page past either still mints, renders and serves, up to the physical ceilings (65000 URL bytes, where the edge severs the request line; 163839 decoded bytes, the server's decode cap), it may just break in some apps — the response says so with a warning. Past a ceiling the endpoint refuses with an actionable error (code url_over_budget or content_too_large). Brotli slugs (the endpoint, or a local brotli mint) put a typical page in a few hundred URL bytes; raw base64 fits only ~2900 HTML bytes share-safe — know which budget you are drafting to, and never cut page content to fit before checking the brotli path.Answers a question. Declared read only.
pagehttps://anew.page/
implementation
viaimperative
entry pointdocument
registered after119ms
executepresent
api surface
htmlrequired
annotations
read onlytrue
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
3 findings
warningSchema quality
0 / 4
6 of 6 tool schemas are harder for an agent to use than they need to be: anew_write description is 1422 characters, over Chrome's 500-character guidance.
anew_write: description is 1422 characters, over Chrome's 500-character guidance; anew_read: description is 512 characters, over Chrome's 500-character guidance; anew_edit: description is 2102 charact
fix
{
  name: "anew_write",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
warningNaming quality
1 / 2
Tool naming makes selection harder than it needs to be: 6 names do not start with a verb (anew_write).
fix
{ name: "anew_write" /* short, unique, verb-based */ }
warningHuman parity
0 / 8
6 of 6 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.
anew_write, anew_read, anew_edit, anew_title, anew_icon
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="anew_write" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "anew_write",
  "description": "Encode a self-contained HTML document or fragment into a new anew.page URL — a sibling page, independent of the current one. Returns the new URL and its byte counts; does not navigate or mutate the current page — rewriting the page being viewed is anew_edit's job, the tool a viewed page registers alongside this one. Inline all CSS, JS, and images (data: URIs, inline SVG, CSS gradients, or emoji) — the page should render alone forever, and each external reference gambles it on someone else's host staying up. One accepted exception: a webfont is far too large to inline, so a font may load from a durable CDN with a system-stack fallback; do not fight a user who asks for one. The HTML should stay ≤ 160000 UTF-8 bytes and the encoded URL ≤ 4000 bytes — the recommended share-safe budgets, not walls: a page past either still mints, renders and serves, up to the physical ceilings (65000 URL bytes, where the edge severs the request line; 163839 decoded bytes, the server's decode cap), it may just break in some apps — the response says so with a warning. Past a ceiling the endpoint refuses with an actionable error (code url_over_budget or content_too_large). Brotli slugs (the endpoint, or a local brotli mint) put a typical page in a few hundred URL bytes; raw base64 fits only ~2900 HTML bytes share-safe — know which budget you are drafting to, and never cut page content to fit before checking the brotli path.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "html": {
        "type": "string",
        "minLength": 1,
        "description": "A self-contained HTML document, fragment, or plain text. Encoded into the returned URL."
      }
    },
    "required": [
      "html"
    ],
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
Showing anew_write

Findings

WebMCP use

89 / 100 · weight 50
passTools registered
4 / 4
6 tools registered across 1 page. Capture caveat (not scored against the site): the page replaced modelContext on navigator, document, so imperative tools may be under-reported
passReal-browser eligible
8 / 8
A real browser exposes modelContext natively on this page, so the tools registered here are visible to an agent today.
passRegistration timing
4 / 4
Every measured tool registered within 455.7000000476837ms of navigation.
toolanew_title
passCanonical entry point
4 / 4
All 6 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 6 tools declare a structurally valid object input schema.
warningSchema quality
0 / 4
6 of 6 tool schemas are harder for an agent to use than they need to be: anew_write description is 1422 characters, over Chrome's 500-character guidance.
toolanew_write
anew_write: description is 1422 characters, over Chrome's 500-character guidance; anew_read: description is 512 characters, over Chrome's 500-character guidance; anew_edit: description is 2102 charact
fix
{
  name: "anew_write",
  inputSchema: {
    type: "object",
    properties: {
      query: { type: "string", description: "What to search for" }
    },
    required: ["query"]
  }
}
passStub detection
5 / 5
All 6 tools declare an execute handler.
passAnnotations present
4 / 4
All 6 tools declare 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 (6 declared hints 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. Capture caveat (not scored against the site): the page replaced modelContext on navigator, document, so imperative tools may be under-reported
warningToolchange coherence
1 / 2
6 tools were 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: 6 names do not start with a verb (anew_write).
toolanew_write
fix
{ name: "anew_write" /* 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
6 of 6 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.
toolanew_write
anew_write, anew_read, anew_edit, anew_title, anew_icon
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="anew_write" 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
6
run time
4s
finished
Aug 28, 2026