htmlradar-mcp

Name: htmlradar-mcp
Author: com.htmlradar

MCPattestedlive

v0.5.1com.htmlradarAGPL-3.0-or-laterUpdated 9d agonpm GitHub

Send a web page to specific people, control who opens it, see how it was read, and update it.

Endpoint healthlive

checked 3 days ago · 187ms · auth required

100% of the last 4 checks reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

57Downloads/wk

2GitHub stars

1Forks

9d agoLast update

Needs 1 credential before it runs

HTMLRADAR_API_KEYAPI keyrequired
HTMLRadar API key, created at https://htmlradar.com/settings under "API keys". Starts with hr_live_.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorcom.htmlradar

LicenseAGPL-3.0-or-later

Version0.5.1

Sourcenpm+mcp-registry

npmhtmlradar-mcp

GitHubhtmlradar/htmlradar

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 10fc257

Dependencies✓ 0 resolved · none vulnerable

Tool surface—

Security scan✓ Cleanv0.3.1 · 27d agoHow well does this scan work?

EvalsNone

IndexedAug 31, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source27d ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Send a web page to specific people, control who opens it, see how it was read, and update it.

Keywords

mcp

Alternatives

Comparing tool surfaces…

htmlradar-mcp

Tools

Dependency tree