com.htmlradar/share
NPM · HTMLRADAR-MCP · 2 COMPONENTS · SCANNED SEP 20
Publish HTML as a tracked link and see who opened it and which sections they read.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to htmlradar/htmlradar). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1447 tokens (~206/item across 7 items; 7 tools + 0 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 Management60
- Stability observed for 18 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 8 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 com.htmlradar/share MCP server?
com.htmlradar/share runs locally as an npm package, launched with npx -y htmlradar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · htmlradar-mcp
claude mcp add com-htmlradar-share -- npx -y htmlradar-mcp
{
"mcpServers": {
"com-htmlradar-share": {
"command": "npx",
"args": [
"-y",
"htmlradar-mcp"
]
}
}
} {
"servers": {
"com-htmlradar-share": {
"command": "npx",
"args": [
"-y",
"htmlradar-mcp"
]
}
}
} codex mcp add com-htmlradar-share -- npx -y htmlradar-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-htmlradar-share": {
"type": "local",
"command": [
"npx",
"-y",
"htmlradar-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-htmlradar-share --command npx --arg -y --arg htmlradar-mcp
mcp_servers:
com-htmlradar-share:
command: "npx"
args: ["-y", "htmlradar-mcp"] {
"McpServers": {
"com-htmlradar-share": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"htmlradar-mcp"
]
}
}
} assistant mcp add com-htmlradar-share -t stdio -c npx -a -y htmlradar-mcp
{
"mcpServers": {
"com-htmlradar-share": {
"command": "npx",
"args": [
"-y",
"htmlradar-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Package version: 0.2.0 → 0.3.1 functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 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.
- 8 Sept 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.
- 6 Sept 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.
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 · Analysed npm/htmlradar-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | htmlradar/htmlradar |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/htmlradar/htmlradar/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.3.1 |
| Rekor log index | 2696432492 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:34196bcf43e467f253b79a0c4395d9c594052bbcd7f58b8b8e4bf51bf82a1d23810e20f53c656f9a30724e156f182afe653a10578885c47bd2bad6e70 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_share Make another tracked link for an existing document ~300
Creates an additional tracked link for a document already on HTMLRadar, with its own recipient label, gate, password, expiry and address. One link per recipient is what separates their reading reports. It uploads nothing and creates no second copy of the document, and it cannot publish new markup: it takes a document id, which list_shares returns and share_html returned when the document was first published. The link is live the moment it is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_email_domains | array | – | Only these email domains may open the link, e.g. ["acme.com"]. |
| document_id | string | yes | The document to make another link for — the document id from list_shares, or the one share_html returned when the document was first published. |
| expires_in_hours | integer | – | Link stops working after this many hours. |
| lock_deck | boolean | – | Blocks save and print and adds a watermark; default true. Pass false for a document the recipient is meant to keep a copy of. |
| password | string | – | Extra password gate on top of the email gate. |
| recipient_label | string | – | Who this link is for, e.g. "Acme". One link per recipient reads best. |
| require_email | boolean | – | Ask the recipient for their email before the document opens. Defaults to true. |
| slug | string | – | Custom link name, so the URL reads /r/acme-proposal. Paid plans only. |
No output schema declared.
No examples provided.
get_share_activity Check who read a tracked link ~176
Reports whether a tracked HTMLRadar link has been opened, by whom, for how long, how far they scrolled, and which sections held their attention. Per viewer it names the five sections with the most reading time, and every figure is rounded down, so no number it prints is above the recorded one. It accepts a share id, a slug or a link; list_shares returns all three.
| Name | Type | Req | Description |
|---|---|---|---|
| include_detail | boolean | – | Also return each reader's country, city, device and referrer. Off by default: that is a named person's location and device, and whether the document was read and which parts of it is answered without… |
| share_id | string | yes | The share id returned by share_html, or the share's slug (the part after /r/ in its link), or the link itself. |
No output schema declared.
No examples provided.
list_shares List tracked links on this account ~140
Lists the account's tracked links, newest first: the slug, the recipient label, the document title, whether it has been opened and when, and the share and document ids the other tools take. This is where the identifiers for a link made in an earlier conversation come from. Returns at most 50 per call; the `before` cursor pages back through older links.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | Cursor for the next page: the `next_before` value printed at the end of a previous list_shares result, of the form <created_at>|<share id>. Pass it back exactly as printed. Omit for the most recent l… |
No output schema declared.
No examples provided.
replace_document Replace a document, keeping every link ~156
Replaces the contents of a document already on HTMLRadar. Every existing link stays exactly as it is — same address, same settings, same reading history — and serves the new contents from the next time it is opened, so nobody is sent a second link. The new HTML is screened for phishing signals as every upload is, and the previous version is kept in the document's history. Recipients may already have read the old contents, and there is no partial update: the markup supplied replaces the document.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | The document whose contents are being replaced. Every link to it keeps working. |
| html | string | yes | The new HTML markup, in full. It replaces the document; there is no partial update. |
No output schema declared.
No examples provided.
revoke_share Switch a tracked link off ~154
Switches off a tracked link that has already been sent. Anyone who opens it afterwards sees that it is no longer available, and the sender is emailed that somebody tried. This changes what a recipient can see. It is reversible — `revoked: false` switches the link back on — and it deletes nothing: the link, its settings and its whole reading history survive. Deleting a link is possible only on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| revoked | boolean | – | True (the default) switches the link off. False switches it back on. |
| share_id | string | yes | The share id, the share's slug (the part after /r/ in its link), or the link itself. list_shares returns all three. |
No output schema declared.
No examples provided.
share_html Share HTML as a tracked link ~345
Publishes an HTML document — a deck, proposal, report or one-pager — as a tracked HTMLRadar link, and returns two addresses: the link for the recipient, and a dashboard address for the sender. The recipient sees the document as written and never the tracking. The markup goes in `html`; there is no file-path argument, so a document on disk reaches this tool only as markup the caller has already read, which leaves the user's permissions on their own file tools in charge of what is published. The link is live the moment it is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_email_domains | array | – | Only these email domains may open the link, e.g. ["acme.com"]. |
| expires_in_hours | integer | – | Link stops working after this many hours. |
| html | string | yes | The HTML markup to publish, in full. There is no file-path argument: a document on disk reaches this tool only as markup the caller has already read. |
| lock_deck | boolean | – | Blocks save and print and adds a watermark; default true. Pass false for a document the recipient is meant to keep a copy of. |
| password | string | – | Extra password gate on top of the email gate. |
| recipient_label | string | – | Who this link is for, e.g. "Acme". One link per recipient reads best. |
| require_email | boolean | – | Ask the recipient for their email before the document opens. Defaults to true. |
| slug | string | – | Custom link name, so the URL reads /r/acme-proposal. Paid plans only. |
| title | string | – | Name shown on your dashboard. Recipients do not see it. |
No output schema declared.
No examples provided.
whoami Show the HTMLRadar plan and free links left ~40
Reports the plan the HTMLRadar API key's account is on and how many of its free tracked links remain. It returns no account identifier and no email address.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.htmlradar/share MCP server?
com.htmlradar/share is an MCP server listed in the public MCP registry as com.htmlradar/share. Publish HTML as a tracked link and see who opened it and which sections they read. This page covers its npm package (htmlradar-mcp).
Is the com.htmlradar/share MCP server safe to use?
com.htmlradar/share scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 com.htmlradar/share MCP server expose?
com.htmlradar/share exposes 7 tools: share_html, create_share, list_shares, get_share_activity, revoke_share, and 2 more. Their descriptions and schemas cost roughly 1,311 tokens of context every time the server is loaded.
Is the com.htmlradar/share MCP server still maintained?
com.htmlradar/share 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.
What licence is the com.htmlradar/share MCP server under?
com.htmlradar/share declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.