Skip to main content
Glama
AgentiLoop

pagewire

by AgentiLoop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to pagewire

No user-submitted related servers found.

    Related Servers

    • skim-mcp

      JessieJanie
      A
      license
      A
      quality
      C
      maintenance
      Pay-per-use clean web reader for AI agents. URL in, markdown plus metadata out, in milliseconds. Settled per-call in USDC over x402 — no signup, no API keys.
      1
      18 npm
      3
      MIT

    • SmartFetch

      Friezaaaa
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to reliably fetch public web URLs and extract clean, agent-ready text, Markdown, links, and metadata, with automatic browser fallback and optional x402 payment support.
      -

    • x402-md-mcp

      Bigabou007-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables extracting clean Markdown from any webpage by paying $0.005 USDC per call via the x402 protocol, with automatic wallet-based payment settlement.
      3 npm
      MIT

    • read-website-fast

      nathanokada
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients and AI agents to fetch webpages and crawl sites, strip noise, and convert content into clean, link-preserving Markdown with caching and configurable multi-page depth while minimizing token usage.
      MIT

    • read-website-fast

      Razi7728
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP clients to fetch webpages and crawl sites, extract main content, and convert it into clean Markdown with preserved links for fast, token-efficient scraping.
      -
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct output: clean Markdown body, metadata/JSON-LD only, or a multi-page crawl. The descriptions explicitly cross-reference each other ("use page_metadata if you only need title...", "use crawl_site to read the page plus the pages it links to"), leaving no real ambiguity about selection.

    Naming Consistency4/5

    All names are snake_case with a consistent noun/verb structure (page_to_markdown, page_metadata, crawl_site), and the two 'page' tools share a clear prefix. The 'crawl_' verb on the third tool is a minor deviation from the 'page_' prefix pattern but remains readable and descriptive.

    Tool Count5/5

    Three tools is well scoped for a page-fetching service, and each one earns its place by covering a genuinely different retrieval mode (full body, metadata only, small crawl). No redundant or filler tools.

    Completeness4/5

    The surface covers the core fetch lifecycle: single-page content, lightweight metadata, and same-host multi-page crawling, with clear error and pricing semantics. Minor gaps remain around cross-host or larger batch fetching and deeper crawl controls (e.g. page limits, sitemap), but agents can work around these with repeated calls.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources