Skip to main content
Glama
emzimmer

Mozilla Readability Parser MCP Server

by emzimmer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to Mozilla Readability Parser MCP Server

No user-submitted related servers found.

    Related Servers

    • skrape

      AmokOrg
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
      MIT

    • agent-web

      foomworks
      A
      license
      Not graded
      quality
      D
      maintenance
      Converts URLs into clean, LLM-ready markdown, respecting robots.txt and never bypassing anti-bot measures or paywalls.
      MIT

    • cleanfetch

      belzorash
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read web pages reliably, returning clean markdown content, hyperlinks, and metadata without navigation or ad noise.
      3
      6 npm
      MIT

    • Fetch as Markdown

      bhubbb
      F
      license
      Not graded
      quality
      D
      maintenance
      Fetches web pages and converts them to clean, readable markdown format by extracting main content while removing navigation, ads, and other non-essential elements to minimize token usage.
      4
      -
    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.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose focused on parsing webpage content into clean Markdown.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'parse' is straightforward and appropriate for its function.

    Tool Count2/5

    A single tool is too few for a server's purpose, even if that purpose is narrow. This limits functionality and makes the server feel thin, as it lacks complementary operations like configuration, validation, or batch processing that might be expected in a parsing domain.

    Completeness2/5

    The tool surface is severely incomplete for a parsing server. While the 'parse' tool covers the core extraction function, there are obvious gaps such as no tools for handling errors, validating inputs, managing configurations, or providing metadata about the parsing process, which could lead to agent failures in real-world scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources