Skip to main content
Glama
fctpe

web-data-mcp

by fctpe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to web-data-mcp

No user-submitted related servers found.

    Related Servers

    • krwl3r

      garciarsdiego
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.
      1
      MIT

    • crawl4ai-mcp-server

      amienbou121
      -
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server that provides web scraping and crawling tools, integrating seamlessly with AI frameworks like OpenAI Agents SDK, Cursor, and Claude Code.
      4
      -

    • magpie-mcp

      MBemera
      A
      license
      Not graded
      quality
      C
      maintenance
      A secure web scraping MCP server for AI agents that fetches pages with token budgeting, robots.txt compliance, and injection warnings, providing parsed content like markdown, metadata, and structured data.
      1
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: run management, scraping, actor execution, data retrieval, quality validation, retry logic, and RAG conversion. Overlapping tools like scrape_url and run_actor are explicitly differentiated in their descriptions, so an agent can reliably select the correct one.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern (get_run_status, scrape_url, run_actor, fetch_dataset_items, validate_dataset, retry_low_quality_run). The exception is dataset_to_rag_documents, which lacks a leading verb and breaks the pattern, though it remains readable and unambiguous.

    Tool Count5/5

    Seven tools is a well-scoped count for a web data extraction and processing server. Each tool addresses a distinct step in the pipeline without redundancy, making the set feel complete yet not overwhelming.

    Completeness5/5

    The tool surface covers the full lifecycle: initiating extractions (scrape_url/run_actor), monitoring runs (get_run_status), fetching results (fetch_dataset_items), validating quality (validate_dataset), improving results (retry_low_quality_run), and preparing output for downstream use (dataset_to_rag_documents). No critical gaps are apparent for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources