Skip to main content
Glama
dong7812

dompruner-mcp

by dong7812
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to dompruner-mcp

No user-submitted related servers found.

    Related Servers

    • scout

      tools-for-agents
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that fetches web pages, extracts clean markdown (reducing token count), caches results, and provides searchable reading history.
      MIT

    • Lean Reader

      AIMento
      A
      license
      A
      quality
      F
      maintenance
      MCP server that converts URLs into token-minimized clean text for LLMs, providing a receipt of token and cost savings.
      1
      31 npm
      MIT

    • superFetch MCP Server

      j0hanz
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.
      1
      42 npm
      MIT

    • NodeProxy

      pgalyen1987
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that converts web pages to clean Markdown for LLMs via two paid tools: surface_markdown_parser and stealth_markdown_parser.
      330 npm
      -

    • paimon-mcp-fetch

      paimonchan
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server that fetches URLs and returns clean, readable markdown, enabling AI assistants to read any webpage with article extraction, caching, and security features.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: fetching a single URL, fetching multiple pages from a sitemap, and analyzing token reduction. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the consistent 'dompruner_' prefix, but the second part mixes verbs ('fetch', 'analyze') with a noun ('sitemap'). While still readable and predictable, the pattern is not purely verb-based.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to its core purpose of DOM pruning and token reduction. Each tool earns its place and the count is appropriate for the focused domain.

    Completeness5/5

    The tool surface covers all primary workflows: single-URL fetching, whole-sitemap ingestion, and analysis/reporting. No obvious gaps exist for the stated utility.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources