app.htmldrop/mcp
REMOTE · HTMLDROP.APP · 2 COMPONENTS · SCANNED SEP 20
Publish HTML or Markdown from any MCP client to a live, shareable URL on htmldrop.app.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 260 tokens (~86/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 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 (100% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 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
How do I install the app.htmldrop/mcp server?
app.htmldrop/mcp is a hosted endpoint at https://htmldrop.app/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 · htmldrop.app
claude mcp add --transport http app-htmldrop-mcp 'https://htmldrop.app/mcp'
{
"mcpServers": {
"app-htmldrop-mcp": {
"url": "https://htmldrop.app/mcp"
}
}
} {
"servers": {
"app-htmldrop-mcp": {
"type": "http",
"url": "https://htmldrop.app/mcp"
}
}
} [mcp_servers.app-htmldrop-mcp] url = "https://htmldrop.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-htmldrop-mcp": {
"type": "remote",
"url": "https://htmldrop.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-htmldrop-mcp --url 'https://htmldrop.app/mcp' --transport streamable-http
mcp_servers:
app-htmldrop-mcp:
url: "https://htmldrop.app/mcp" {
"McpServers": {
"app-htmldrop-mcp": {
"Transport": "http",
"Url": "https://htmldrop.app/mcp"
}
}
} assistant mcp add app-htmldrop-mcp -t streamable-http -u 'https://htmldrop.app/mcp'
{
"mcpServers": {
"app-htmldrop-mcp": {
"type": "http",
"url": "https://htmldrop.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.3.2 → 0.3.4 functional
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 20 Sept 2026 · Probed https://htmldrop.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=htmldrop.app | CN=YE1,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 55ab5cbcb33b7b025224d5c77654caa9a16 |
| SANs: *.htmldrop.app, htmldrop.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 insecure
Validation of htmldrop.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| htmldrop.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://htmldrop.app/.well-known/oauth-protected-resource", scope="mcp"
Bearer resource_metadata="https://htmldrop.app/.well-known/oauth-protected-resource", scope="mcp"Protected resource metadata
| Document | https://htmldrop.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://htmldrop.app/mcp |
| Authorisation server | https://htmldrop.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://htmldrop.app/mcp | Verified | 200 | |
| http (plaintext) | http://htmldrop.app/mcp | HTTPS enforced | 301 | https://htmldrop.app/mcp |
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 →
htmldrop_delete ~65
Delete a site by its id. The id is the opaque string returned from htmldrop_list (NOT the slug). Once deleted the public URL returns 404 immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The site's id, as returned by htmldrop_list. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | Always true on success. |
| id | string | yes | The deleted site's id. |
No examples provided.
htmldrop_list ~31
List every site the authenticated tenant has published. Returns each site's slug, id, and public URL.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| sites | array | yes | Every published site for the authenticated tenant. |
No examples provided.
htmldrop_publish ~164
Publish an HTML or Markdown document as a hosted page on htmldrop. Returns the public share URL. Use this whenever a user asks to publish, share, or 'put on the web' some HTML / Markdown content. Pass exactly one of `html` or `markdown`.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | Raw HTML document content. Either this or `markdown` must be set. |
| markdown | string | – | Markdown content. Will be rendered to HTML on the server. Either this or `html` must be set. |
| slug | string | – | Optional URL slug (3-63 chars, lowercase letters, numbers, hyphens). If omitted, a random slug is assigned. |
| title | string | – | Optional title shown in the dashboard list. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Opaque site id. Pass to htmldrop_delete to remove later. |
| slug | string | yes | Resolved slug for the published site. |
| url | string | yes | Public share URL of the published page. |
No examples provided.
What is the app.htmldrop/mcp server?
app.htmldrop/mcp is listed in the public MCP registry as app.htmldrop/mcp. Publish HTML or Markdown from any MCP client to a live, shareable URL on htmldrop.app. This page covers its hosted endpoint (https://htmldrop.app/mcp).
Is the app.htmldrop/mcp server safe to use?
app.htmldrop/mcp scores 92 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 app.htmldrop/mcp server expose?
app.htmldrop/mcp exposes 3 tools: htmldrop_publish, htmldrop_list, htmldrop_delete. Their descriptions and schemas cost roughly 260 tokens of context every time the server is loaded.
Does the app.htmldrop/mcp server require authentication?
Yes. app.htmldrop/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the app.htmldrop/mcp server still maintained?
app.htmldrop/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.