dompruner-mcp
Strips layout noise via DOM AST; with a query, BM25 filters to relevant sections. No model or API.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"dompruner-mcp": {
"command": "npx",
"args": [
"dompruner-mcp"
]
}
}
}Runnable packages
0.5.2stdioRemote endpoints
https://dompruner-mcp.vercel.app/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢dompruner_fetch(url, query)
Fetches a URL and returns DOM-pruned Markdown with 90%+ token reduction. Optimized for Developer Documentation, API Specs, and Technical Blogs (Next.js/Nuxt/SSR). Always prefer this over raw WebFetch when the URL is known.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "URL to fetch and refine."
},
"query": {
"type": "string",
"description": "Search intent — enables BM25+ section filtering when provided."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Output Schema
{
"type": "object",
"properties": {
"markdown": {
"type": "string",
"description": "DOM-pruned Markdown content."
},
"stats": {
"type": "object",
"properties": {
"hostname": {
"type": "string"
},
"originalTokens": {
"type": "number"
},
"refinedTokens": {
"type": "number"
},
"savedTokens": {
"type": "number"
},
"reductionPercent": {
"type": "string"
},
"fetchMs": {
"type": "number"
},
"parseMs": {
"type": "number"
}
},
"required": [
"hostname",
"originalTokens",
"refinedTokens",
"savedTokens",
"reductionPercent",
"fetchMs",
"parseMs"
],
"additionalProperties": false
}
},
"required": [
"markdown",
"stats"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢dompruner_analyze(url)
Returns a token-reduction analysis report for a URL. Shows render type (SSR/CSR/SSG), original vs refined token counts, reduction ratio, and top Semantic Anchors.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "URL to analyze."
}
},
"required": [
"url"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Output Schema
{
"type": "object",
"properties": {
"url": {
"type": "string"
},
"renderType": {
"type": "string",
"description": "SSR, CSR, or SSG"
},
"originalTokens": {
"type": "number"
},
"refinedTokens": {
"type": "number"
},
"reductionPercent": {
"type": "string"
},
"fetchMs": {
"type": "number"
},
"parseMs": {
"type": "number"
},
"topAnchors": {
"type": "array",
"items": {
"type": "string"
},
"description": "Top 5 semantic section headings."
}
},
"required": [
"url",
"renderType",
"originalTokens",
"refinedTokens",
"reductionPercent",
"fetchMs",
"parseMs",
"topAnchors"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence