Skip to content

Hypertext MCP server

live.hypertext/hypertexthypertext.livestreamable-httpv1.0.0Scanned

Publish complete HTML artifacts and return a public share URL.

1 tool: 1 do something that can't be undone.

Tools: 0 delete, 1 irreversible, 0 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Hypertext MCP server can do

The Hypertext MCP server is published by hypertext.live, a domain the MCP Registry verified. It has 1 tool. It can do things that cannot be undone, such as sending, paying or publishing (publish_html), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (publish_html).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 1.0.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.

1 tool

Can't be undone 1Claude Code: ask
  • publish_htmlPublish a finished HTML artifact, report, dashboard, visualization, prototype, or interactive document and return a public share URL.Can send data outNo findings

    Why it is in this group

    • The name "publish_html" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_html" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publish a finished HTML artifact, report, dashboard, visualization, prototype, or interactive document and return a public share URL. Use when an agent has generated browser-ready HTML that should be shared outside the chat or workspace.

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 or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-11-25 to none

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.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-11-25 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http hypertext https://hypertext.live/mcp
claude mcp add --transport http hypertext https://hypertext.live/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__hypertext__publish_html"
    ],
    "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 hypertext. Review it before you use it.

Capability tags behind 1 rule
  • mcp__hypertext__publish_html outbound

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/live.hypertext/hypertext/verify?hash=bcd09036b905ba164bbf4313259db9c56ff0544afe5e183f3019b62edddd7be1" | jq -e '.changed == false'

Pinned hash bcd09036b905, from Oct 21, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/live.hypertext/hypertext/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for live.hypertext/hypertext
[![Anlyon Radar](https://radar.anlyon.com/badge/live.hypertext/hypertext.svg)](https://radar.anlyon.com/servers/live.hypertext/hypertext)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

Hypertext MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hypertext MCP server safe?

No scan can promise that. What its definitions show: 1 tool, 1 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 Hypertext MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hypertext MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_html.

What tools does the Hypertext MCP server have?

1 tool: 1 irreversible. publish_html.

Does the Hypertext MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Hypertext MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_html.

Has the Hypertext MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.