Skip to main content
Glama
Llamatron2112

mcp-dom-extract

by Llamatron2112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-dom-extract

No user-submitted related servers found.

    Related Servers

    • Scraper.is MCP Server

      Ai-Quill
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables extracting data from websites using natural language prompts, allowing users to specify exactly what content they want in plain English and returning structured JSON data.
      32 npm
      8
      MIT

    • browserless

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables headless-Chromium web automation, including rendering fully-executed HTML, extracting structured data with CSS selectors, capturing screenshots, and AI-assisted smart scraping of web pages.
      MIT

    • Ashra Structured Data

      getrupt
      -
      license
      Not graded
      quality
      C
      maintenance
      Extract structured data from any website with a simple SDK call. No scraping code, no headless browsers - just prompt and get JSON.
      62
      -

    • Browser MCP Server

      persi123
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to understand web page structure and content through structured data extraction and element discovery using Playwright, eliminating the need for screenshots.
      4
      7 npm
      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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have clear, distinct roles: structure inspection, selector discovery, selector probing, and extraction. The only slight overlap is between extract_data_from_url and extract_page_text, since both can retrieve content via CSS selectors, but the former emphasizes precise structured data while the latter focuses on readable text.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: extract_data, extract_page, inspect_page, discover_selectors, probe_selectors. The 'from_url' suffix on one tool is a minor variation but does not break the overall predictability.

    Tool Count5/5

    Five tools is well-scoped for a DOM extraction server. Each tool represents a distinct step in the workflow of inspecting, discovering, probing, and extracting, with no redundancy or bloat.

    Completeness5/5

    The tool surface covers the full practical workflow for DOM extraction: inspect structure to understand the page, discover candidate selectors, probe selectors to verify them, then extract either precise data or readable text. There are no obvious dead ends or missing critical operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources