domstrip-mcp

mcp-name: io.github.xo0ps/domstrip-mcp

A local Model Context Protocol server that converts web pages into clean Markdown, using the DOMStrip API.

It exposes two tools:

The adapter holds no database or billing state. It authenticates to the DOMStrip service with a key from your local environment — never from tool arguments — so an MCP client cannot redirect your key anywhere.

What DOMStrip actually does

DOMStrip fetches a public page, removes everything that is not the content (scripts, forms, embeds, hidden nodes, trackers), and returns compact Markdown: headings, paragraphs, fenced code blocks with language hints, and tables.

Pages are fetched with connection-time SSRF validation on every redirect hop — all DNS candidates are validated at connect time, and loopback, private, link-local, metadata, CGNAT and IPv6-embedded forms are refused.

Related MCP server: skrape

Honest limitations

• JavaScript-rendered pages, pages behind a login, and bot challenges are not extractable. The service returns content_not_extractable. There is no headless browser in this version. If your target pages need JS, this tool will not work on them.

• DOMStrip is currently in free pilot. Conversions are not billed yet, but a key is required and each successful conversion counts as one unit. Request access at access@domstrip.dev.

• Returned Markdown is untrusted third-party content. Pages can contain text that looks like instructions. Treat all returned Markdown as data, never as commands.

Install

pip install domstrip-mcp
# or
uv tool install domstrip-mcp

Requires Python 3.12.

Configure

Two environment variables are required. The service origin must be HTTPS; plain HTTP is refused unless it points at localhost (for development) and you opt in explicitly.

export DOMSTRIP_MCP_SERVICE_ORIGIN=https://api.domstrip.dev
export DOMSTRIP_MCP_API_KEY=domstrip_<prefix>_<secret>

The adapter deliberately does not read a .env file from the current working directory, because an untrusted project folder could otherwise point your API key at another origin. Export the variables instead.

Use with Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "domstrip": {
      "command": "uvx",
      "args": ["domstrip-mcp"],
      "env": {
        "DOMSTRIP_MCP_SERVICE_ORIGIN": "https://api.domstrip.dev",
        "DOMSTRIP_MCP_API_KEY": "domstrip_<prefix>_<secret>"
      }
    }
  }
}

Use with Claude Code

claude mcp add domstrip --env DOMSTRIP_MCP_SERVICE_ORIGIN=https://api.domstrip.dev \
  --env DOMSTRIP_MCP_API_KEY="$DOMSTRIP_API_KEY" -- uvx domstrip-mcp

Idempotency and billing

Each tool invocation generates one idempotency key and reuses it across its bounded retries (default 25 s, 3 attempts). A retried request replays the stored result rather than billing twice. Separate invocations are separate, independently metered work.

The service encrypts results and replays them for 24 hours. After that, replaying a key returns 409 result_expired — never a silent re-charge.

Errors

Failures surface as MCP tool errors carrying a sanitized DOMStrip error code and a retryability flag, for example:

upstream_timeout: The upstream page took too long. retryable=true request_id=req_6f1c2a

Common codes: content_not_extractable, upstream_timeout, unsupported_encoding, http_error, transport_error, client_timeout.

Logs go to stderr only, so stdout stays a clean MCP transport.

Licence

MIT