Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

anew

REMOTE · ANEW.PAGE

Encode self-contained HTML pages into shareable URLs.

Available components

0 this week 89 Trust /100

Last scanned (21 hours ago)

Scores higher than 97% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1641 tokens (~273/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 12 Oct 26 0
    • Resource “anew-editor” now points somewhere else: ui://anew/editor/7 → ui://anew/editor/13 security
    • Resource “anew-page-view” now points somewhere else: ui://anew/page-view/6 → ui://anew/page-view/12 security
    • Tool “anew_page” changed its title: Page Editor → anew cosmetic
  • 3 Oct 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “anew_write” rewrote its description, which is the text the model reads security
  • 2 Oct 26 +1
    • Resource “anew-page-view” now points somewhere else: ui://anew/page-view → ui://anew/page-view/2 security
    • Tool “anew_write” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 50% ▼ functional
    • Schema quality: 544 → 280 ▲ functional
    • Destructive annotations: pass → 100 functional
    • New resource “anew-editor” functional
    • New tool “anew_editor” functional
    • New tool “anew_page” functional
    • “anew_write” reworded the description of “html” cosmetic
    • “anew_write” reworded the description of “javascript” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 17 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “anew_write” rewrote its description, which is the text the model reads security
  • 15 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “anew_write” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://anew.page/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=anew.page CN=YE2,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA384 63c658aefcfe51a3f7991c6f0f18641afc8
SANs: anew.page
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of anew.page. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
page. present 64712 8 Verified
anew.page. present 2371 13 Verified
anew.page. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://anew.page/mcp Verified 200
http (plaintext) http://anew.page/mcp HTTPS enforced 301 https://anew.page/mcp
MCP tools · 4 exposed · ~833 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
anew_editor ~29

Open anew from the sidebar: the editor, fullscreen, on a new blank page. Takes no arguments.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

anew_page ~122

Open a page in the anew editor beside the chat, so the user can edit it by hand: pass an anew.page URL to open that page, or nothing for a new blank page. The editor reports the page it holds back to the chat after every edit. Call it only when the user asks to open the editor or to edit a page themselves; anew_write and anew_read do everything else.

NameTypeReqDescription
urlstring–An anew.page URL or bare slug to open in the editor. Omit it, or leave it empty, for a new blank page.

No output schema declared.

No examples provided.

anew_read ~291

Pass an anew.page URL, get back the HTML document encoded in it, plus its canonical URL and byte size. (Two in-page tools share this name and take no arguments: the editor's reads the document open in the editor, and a rendered page's reads the page being viewed. This one takes a url and reads that page.) To revise an existing anew page, its URL is its source: read it, edit that HTML, write it again. The new URL is a separate page and the original keeps working. Read returns the author's exact bytes — no anew-injected tags, no proxied image srcs — so it re-encodes byte-for-byte. Never re-author from a rendered page, a scraped DOM, or a screenshot: each loses the author's markup, and none is faster than reading the slug. Decoding is local and exact, so any anew URL reads — the page needs no prior visit and no fetch.

NameTypeReqDescription
formatstring–How the document rides back. "text" (default) is one plain text block. "resource" is one embedded-resource block ({type:"resource"}, mimeType text/html) — the typed MCP form for callers that want the…
urlstringyesAn anew.page URL, or a bare slug. Subdomain, cosmetic-prefix and #hash forms all resolve.
NameTypeReqDescription
bytesintegeryesEncoded URL length in bytes.
urlstringyesCanonical anew.page URL for this document.

No examples provided.

anew_write ~391

Publish a web page: encode one self-contained HTML document (or fragment, or plain text) into an anew.page URL and return that URL. Use it when the user asks for a page, a site or a link they can open and share. The page is carried in the URL itself — no account, and no copy of the page is kept — so anyone who has the URL can open it; each call also starts a screenshot of the page, cached publicly for link previews. Put markup and inline CSS in html and any JavaScript in javascript as plain source; the server inserts it before </body>. Inline the page's CSS, scripts and images so it renders on its own; a webfont may load from a CDN. Each encoding path is deterministic: the same input through the same path always produces the same URL. Different paths use different Brotli encoders, though, so the same HTML may mint different — equally valid — URLs; compare pages by their decoded HTML, never by slug. Limits: a page whose URL would pass 4000 bytes, or whose HTML passes 1048576 bytes decoded, is refused with an error that states the size and the overage; apps cut longer links short when they are shared. To revise an existing anew page, its URL is its source: read it, edit that HTML, write it again. The new URL is a separate page and the original keeps working. Read it with anew_read first, then call this with the edited HTML.

NameTypeReqDescription
htmlstringyesThe page: HTML markup with inline CSS — a full document, a fragment, or plain text. Its JavaScript goes in javascript. Encoded into the returned URL.
javascriptstring–Optional client-side JavaScript for the page, as plain source without script tags. The server inserts it immediately before </body> (or at the end when there is no body).
NameTypeReqDescription
bytesintegeryesEncoded URL length in bytes.
decoded_bytesintegeryesThe submitted HTML in UTF-8 bytes.
urlstringyesThe anew.page URL of the page.
warningstring–Not returned: a page past a size limit is refused with an error instead.

No examples provided.

Install

How do I install the anew MCP server?

anew is a hosted endpoint at https://anew.page/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · anew.page

# add to Claude Code
claude mcp add --transport http page-anew-anew 'https://anew.page/mcp'
Common questions

What is the anew MCP server?

anew is an MCP server listed in the public MCP registry as page.anew/anew. Encode self-contained HTML pages into shareable URLs. This page covers its hosted endpoint (https://anew.page/mcp).

Is the anew MCP server safe to use?

anew scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the anew MCP server expose?

anew exposes 4 tools: anew_write, anew_read, anew_page, anew_editor. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.

Does the anew MCP server require authentication?

No. We connected to anew without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the anew MCP server still maintained?

anew is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.