dompruner-mcp
NPM · DOMPRUNER-MCP · 2 COMPONENTS
Strips layout noise via DOM AST; with a query, BM25 filters to relevant sections. No model or API.
Available components
Last scanned (5 hours ago)
Scores higher than 85% of npm servers
Category Web Scraping
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 78 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 4 Nov 26 −2
- Stability: pass → 0.90 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/dompruner-mcp@0.5.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dompruner_analyze ~48
Returns a token-reduction analysis report for a URL. Shows render type, original vs refined token counts, and top Semantic Anchors.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL to analyze |
No output schema declared.
No examples provided.
dompruner_fetch ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
dompruner_sitemap ~222
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/).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | URL of the sitemap.xml (e.g. https://example.com/sitemap.xml) |
No output schema declared.
No examples provided.
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.
npm · dompruner-mcp
claude mcp add dong7812-dompruner-mcp -- npx -y dompruner-mcp
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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 6 November 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.
What did VerifyMCP test on the dompruner-mcp server?
VerifyMCP ran 16 checks on dompruner-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.