HTMLAnnotate MCP server
com.htmlannotate/htmlannotatehtmlannotate.comstreamable-httpv1.1.0Scanned
Share pages for review, then read, reply to and resolve comments. Sign in to keep pages.
6 tools: 2 do something that can't be undone, 3 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the HTMLAnnotate MCP server can do
The HTMLAnnotate MCP server is published by htmlannotate.com, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (share_html and reply_to_comment) and create or change data (3 tools: share_url, resolve_comment and update_page), but cannot delete data. 1 tool only reads.
6 tools bring in text other people can write (share_html, share_url, get_comments and 3 more); 3 tools can send data out of your system (share_html, share_url and reply_to_comment).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 2Claude Code: ask
reply_to_commentPost a reply under one comment on an HTMLAnnotate page, as the page owner.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "reply_to_comment" says "reply": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "reply_to_comment" says "reply": it sends or publishes something to other people.
Description, as the server wrote it Post a reply under one comment on an HTMLAnnotate page, as the page owner. Everyone in that thread gets an email. Confirm the wording with the user first.
Annotations the server declares
- title: Reply to a comment
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Changes things 3Claude Code: ask
resolve_commentMark a comment on an HTMLAnnotate page as resolved (done), or reopen it.Reads text others writeNo findings
Why it is in this group
- The name "resolve_comment" says "resolve": a word for reading.
- The description's first verb is "mark": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe name "resolve_comment" says "resolve" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "mark" and "comment": it reads comments, which other people can write.
Description, as the server wrote it Mark a comment on an HTMLAnnotate page as resolved (done), or reopen it. Use after the requested change has been made. Everyone in the thread gets an email when it is resolved.
Annotations the server declares
- title: Mark a comment resolved
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
update_pageReplace an HTML page on HTMLAnnotate with a new version, on the same review link, so the client sees the update without a new link.Reads text others writeNo findings
Why it is in this group
- The name "update_page" says "update": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Replace an HTML page on HTMLAnnotate with a new version, on the same review link, so the client sees the update without a new link. The new version starts with no comments; earlier versions keep theirs. Use after making the changes from get_comments. Needs the manage link. Only for pages shared as HTML, not live websites.
Annotations the server declares
- title: Publish a new version of a page
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
get_commentsRead every comment on an HTMLAnnotate page: what each reviewer said, which element it is pinned to (with a CSS selector), the screen size, the page version it was left on, suggeste…Reads text others writeNo findings
Why it is in this group
- The name "get_comments" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_comments" says "get" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "comment": it reads comments, which other people can write.
Description, as the server wrote it Read every comment on an HTMLAnnotate page: what each reviewer said, which element it is pinned to (with a CSS selector), the screen size, the page version it was left on, suggested text changes and replies. Use it when the user asks what their client said, or wants you to make the requested changes. Needs the page's private manage link (returned by share_html or share_url, or pasted by the user).
Annotations the server declares
- title: Read the feedback on a page
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (2 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.htmlannotate.com: tools/list returned 6 tools to an anonymous client, including share_html (irreversible), reply_to_comment (irreversible), share_url (write), resolve_comment (write), update_page (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:get_commentsOnly readsdescription
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http htmlannotate https://mcp.htmlannotate.comclaude mcp add --transport http htmlannotate https://mcp.htmlannotate.comRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__htmlannotate__get_comments"
],
"ask": [
"mcp__htmlannotate__share_html",
"mcp__htmlannotate__share_url",
"mcp__htmlannotate__reply_to_comment",
"mcp__htmlannotate__resolve_comment",
"mcp__htmlannotate__update_page"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as htmlannotate. Review it before you use it.
Capability tags behind 6 rules
- mcp__htmlannotate__share_html untrusted-input, outbound
- mcp__htmlannotate__share_url untrusted-input, outbound
- mcp__htmlannotate__get_comments untrusted-input
- mcp__htmlannotate__reply_to_comment untrusted-input, outbound
- mcp__htmlannotate__resolve_comment untrusted-input
- mcp__htmlannotate__update_page untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.htmlannotate/htmlannotate/verify?hash=d46886566152181d1ad895c9bbbe4eafa3b4803fbd9cc9067aa0994eea4b5e45" | jq -e '.changed == false'Pinned hash d46886566152, from Nov 18, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.htmlannotate/htmlannotate/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.htmlannotate/htmlannotate)Source: MCP Registry. Synced Nov 18, 2026, 18:17 UTC.
HTMLAnnotate MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the HTMLAnnotate MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the HTMLAnnotate MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the HTMLAnnotate MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: share_html and reply_to_comment.
What tools does the HTMLAnnotate MCP server have?
- 6 tools: 2 irreversible, 3 write, 1 read. share_html, reply_to_comment, share_url, resolve_comment, update_page and get_comments.
Does the HTMLAnnotate MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the HTMLAnnotate MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): share_html, share_url and reply_to_comment.
Has the HTMLAnnotate MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.