Skip to main content
Glama

Related Servers

Alternatives to ToolSnap MCP

  • A
    license
    A
    quality
    B
    maintenance
    42 local SEO tools for AI assistants. SERP tracking, Google Business Profile data, review monitoring, keyword research, AI visibility scoring, geogrid rank scans, citation audits, and competitive analysis.
    53
    53 npm
    3
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Read any public web page, or up to 20 in one batch, as a clean AIDocument: Markdown plus title, description, structure, and provenance, with navigation and boilerplate stripped. Reads are served through Lyrenth's own independently built web index, so each costs a fraction of the tokens of raw HTML and is origin-friendly. A third tool reports your plan and how many reads you have used.
    3
    103 npm
    1
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server providing 11 pay-per-call web intelligence tools (page reading, PDF extraction, RSS parsing, screenshots, summarization, structured data extraction) for AI agents, paid automatically in USDC via the x402 protocol on Base mainnet with no API keys required.
    38 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    MCP server that enables AI agents to fetch web content as clean, structured Markdown via NanoParse's hosted API, using x402 micropayments in USDC on Base.
    1
    31 npm
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server providing 17 keyless, pay-per-use web-data tools with signed-provenance receipts, enabling AI agents to autonomously fetch, extract, and verify web content on Base mainnet.
    48 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Gives AI agents web pages as clean Markdown, links, metadata or JSON that follows your schema. Each call is paid in USDC on Base via x402 ($0.002-$0.02), with built-in spending limits.
    10
    302 npm
    MIT

TDQS

A4.1/5.0

Scored across 17 tools

Disambiguation4/5

Most tools target clearly distinct resource/action combinations, and descriptions explicitly route between similar tools. There is still some overlap between fetch_html, fetch_extract, and html_to_markdown, and use_tool is a generic wrapper that could be confused with direct calls, though the descriptions mitigate this.

Naming Consistency3/5

All names use snake_case and are readable, but the naming patterns are mixed: fetch_html, csv_query, sitemap_parse, memory_snippet, pricing, and html_to_markdown do not follow one predictable verb_noun or resource_action convention. This is mixed but still understandable rather than chaotic.

Tool Count4/5

Seventeen tools is slightly above the typical ideal range, but the server covers a broad set of extraction, metadata, pricing, catalog, and paid utility functions. Each top-level tool has a reasonably distinct role, though a few fetch variants could potentially be consolidated.

Completeness4/5

The surface covers the main web/data extraction formats (HTML, text, metadata, Markdown, PDF, CSV, JSON, sitemap, RSS) plus catalog, pricing, recipes, screenshots, and a wrapper for missing catalog tools. Minor gaps remain around OCR, direct JS rendering, and large-file query variants, but these are documented or reachable through the catalog wrapper.

Maintenance

ActivityActive
ResponsivenessLimited data