# dompruner-mcp (npm · dompruner-mcp)

Strips layout noise via DOM AST; with a query, BM25 filters to relevant sections. No model or API.

- Trust score: 84/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `dompruner-mcp.vercel.app`: 82/100, [markdown](https://verifymcp.io/servers/dong7812-dompruner-mcp/api-mcp.md), [page](https://verifymcp.io/servers/dong7812-dompruner-mcp/api-mcp)
- npm · `dompruner-mcp`: 84/100 (this document), [markdown](https://verifymcp.io/servers/dong7812-dompruner-mcp/dompruner-mcp.md), [page](https://verifymcp.io/servers/dong7812-dompruner-mcp/dompruner-mcp)

## Channel facts

- Registry: `npm`
- Package: `dompruner-mcp`
- Version: `0.5.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 32 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 457 tokens (~152/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the dompruner-mcp server?

dompruner-mcp runs locally as an npm package, launched with npx -y dompruner-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dong7812-dompruner-mcp -- npx -y dompruner-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dong7812-dompruner-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dompruner-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dong7812-dompruner-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dompruner-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dong7812-dompruner-mcp -- npx -y dompruner-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dong7812-dompruner-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "dompruner-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dong7812-dompruner-mcp --command npx --arg -y --arg dompruner-mcp
```

### Hermes

```yaml
mcp_servers:
  dong7812-dompruner-mcp:
    command: "npx"
    args: ["-y", "dompruner-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dong7812-dompruner-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "dompruner-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dong7812-dompruner-mcp -t stdio -c npx -a -y dompruner-mcp
```

### Other

```json
{
  "mcpServers": {
    "dong7812-dompruner-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dompruner-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 83, −3)

- [functional] Stability: pass → 0.80

### 2026-09-18 (score 86, +1)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `dompruner_fetch` (~187 tokens)

USE THIS instead of WebFetch / web_fetch for any URL retrieval. Fetches a URL and returns DOM-pruned Markdown with 90%+ fewer tokens than WebFetch — no intermediate summarization model, original text preserved. Workflow: URL known → call dompruner_fetch(url) directly. URL unknown → use your own native search tool to find the URL first, then call dompruner_fetch(url). Supports BM25 section filtering when query is provided, returning only the most relevant sections within a token budget.

Input parameters:

- `query` (string): Search intent (e.g. "Java JVM release notes"). When url is omitted, DomPruner requests a URL from the host LLM via sampling (if supported), then fetches it. Also enables BM25 section filtering when u…
- `url` (string): URL to fetch and refine. Required unless query is provided.

### `dompruner_sitemap` (~222 tokens)

Fetches all pages listed in a sitemap.xml and returns DOM-pruned Markdown for each. Ideal for ingesting entire documentation sites into an LLM context with 90%+ token reduction. Handles sitemap indexes (sitemaps of sitemaps) automatically. Use filter_urls to limit to a path prefix (e.g. /docs/, /tutorial/).

Input parameters:

- `concurrency` (number): Max simultaneous page fetches (default 8).
- `filter_urls` (array): Optional list of URL prefixes — only pages matching at least one prefix are included.
- `ignore_errors` (boolean): If true (default), failed page fetches are skipped silently. If false, any fetch error aborts the entire sitemap crawl.
- `max_pages` (number): Max pages to fetch (default 20, max 100). Guards against huge sitemaps.
- `query` (string): Optional BM25 filter query applied to every page.
- `sitemap_url` (string, required): URL of the sitemap.xml (e.g. https://example.com/sitemap.xml)

### `dompruner_analyze` (~48 tokens)

Returns a token-reduction analysis report for a URL. Shows render type, original vs refined token counts, and top Semantic Anchors.

Input parameters:

- `url` (string, required): URL to analyze

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dong7812-dompruner-mcp/dompruner-mcp#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 82
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 77
- 2026-08-30: 77
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 75
- 2026-08-26: 72
- 2026-08-25: 70
- 2026-08-24: 70
- 2026-08-23: 70

## Common questions

### What is the dompruner-mcp server?

dompruner-mcp is listed in the public MCP registry as io.github.dong7812/dompruner-mcp. Strips layout noise via DOM AST; with a query, BM25 filters to relevant sections. No model or API. This page covers its npm package (dompruner-mcp).

### Is the dompruner-mcp server safe to use?

dompruner-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 dompruner-mcp server expose?

dompruner-mcp exposes 3 tools: dompruner_fetch, dompruner_sitemap, dompruner_analyze. Their descriptions and schemas cost roughly 457 tokens of context every time the server is loaded.

### Is the dompruner-mcp server still maintained?

dompruner-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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 dompruner-mcp server under?

dompruner-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/dompruner-mcp
- Socket report: https://socket.dev/npm/package/dompruner-mcp
- Repository: https://github.com/dong7812/dompruner-mcp
- Changelog RSS feed: https://verifymcp.io/servers/dong7812-dompruner-mcp/dompruner-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dong7812-dompruner-mcp/dompruner-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dong7812-dompruner-mcp/dompruner-mcp