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.

HTMLpad

REMOTE · HTMLPAD.ORG

Publish HTML pages and get a shareable link. Create, update and read pads on htmlpad.org.

Available components

+4 this week 64 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 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 Security46
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 277 tokens (~92/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 60

    First indexed and scored.

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 21 Nov 2026 · Probed https://htmlpad.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=htmlpad.org CN=WE1,O=Google Trust Services,C=US 12 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA256 db4c17a09a3434340eb5c9a6ac648481
SANs: htmlpad.org, www.htmlpad.org, *.www.htmlpad.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of htmlpad.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
htmlpad.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://htmlpad.org/mcp Verified 200
http (plaintext) http://htmlpad.org/mcp Inconclusive 405
MCP tools · 3 exposed · ~235 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
get_pad ~38

Get the HTML of a public pad on HTMLpad.

NameTypeReqDescription
addressstringyesThe pad address, as in htmlpad.org/<address>/.

No output schema declared.

No examples provided.

publish_html ~111

Publish an HTML page on HTMLpad and get a public link to share. Returns the link, a private edit link and an edit token. Free pads stay online for 90 days. Pages may not contain password or payment card fields.

NameTypeReqDescription
addressstring–Optional address for the page, as in htmlpad.org/<address>/. Letters, numbers, dots, dashes or underscores, up to 64.
htmlstringyesA complete HTML document or fragment, up to 512 KB.

No output schema declared.

No examples provided.

update_pad ~86

Replace the HTML of a pad you published, using the edit token returned by publish_html. Saving also resets its 90 days.

NameTypeReqDescription
addressstringyesThe pad address, as in htmlpad.org/<address>/.
edit_tokenstringyesThe edit token returned when the pad was published.
htmlstringyesThe new HTML, up to 512 KB.

No output schema declared.

No examples provided.

Install

How do I install the HTMLpad MCP server?

HTMLpad is a hosted endpoint at https://htmlpad.org/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 · htmlpad.org

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

What is the HTMLpad MCP server?

HTMLpad is an MCP server listed in the public MCP registry as org.htmlpad/htmlpad. Publish HTML pages and get a shareable link. Create, update and read pads on htmlpad.org. This page covers its hosted endpoint (https://htmlpad.org/mcp).

Is the HTMLpad MCP server safe to use?

HTMLpad scores 64 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 HTMLpad MCP server expose?

HTMLpad exposes 3 tools: publish_html, update_pad, get_pad. Their descriptions and schemas cost roughly 235 tokens of context every time the server is loaded.

Does the HTMLpad MCP server require authentication?

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

Is the HTMLpad MCP server still maintained?

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

What did VerifyMCP test on the HTMLpad MCP server?

VerifyMCP ran 12 checks on HTMLpad, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about HTMLpad: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.