Skip to main content
Glama

Related Servers

Alternatives to ToolSnap MCP

  • A
    license
    A
    quality
    A
    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.
    42
    49 npm
    3
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Read any public web page as a clean AIDocument: Markdown plus title, description, and structure, with navigation and boilerplate stripped. Reads resolve through Lyrenth's shared cache, so it is far fewer tokens than raw HTML and origin-friendly.
    3
    37 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.
    20 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
    16 npm
    MIT
  • A
    license
    Not graded
    quality
    F
    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.
    14 npm
    MIT
  • A
    license
    Not graded
    quality
    F
    maintenance
    Pay-per-call MCP server for WebberSites x402 Data API, offering 45 tools for AI agents: web scraping, document extraction, SEO audits, linting, crypto data, and more, with payment via USDC on Base.
    23 npm
    MIT

TDQS

B3.4/5.0

Scored across 17 tools

Disambiguation4/5

Most tools have clearly distinct purposes: fetch/extract, metadata, Markdown, PDF, CSV, JSON, sitemap, RSS, screenshots, and paid research/image tools. The main overlap is among fetch_extract, fetch_html, html_to_markdown, and fetch_metadata, which all fetch URLs but return different representations, and the descriptions mostly clarify those boundaries.

Naming Consistency3/5

All names use snake_case, but the convention mixes verb-first names like fetch_extract and remove_background with resource-first names like csv_query, sitemap_parse, and screenshot_url. There are also noun-only/meta names such as pricing and tool_catalog, so the pattern is readable but not predictable.

Tool Count4/5

17 tools is slightly heavy but reasonable for a broad web-data toolkit that spans fetching, extraction, parsing, paid APIs, and discovery/meta-helpers. Each tool appears to cover a meaningful capability rather than redundant variations.

Completeness4/5

The surface covers the apparent web-data domain well: page fetching, text/HTML/Markdown/metadata extraction, PDFs, CSV, JSON, sitemaps, RSS, screenshots, keyword research, and background removal. Minor gaps remain around JS-rendered pages and general authenticated/POST API access, though use_tool may partially mitigate undisclosed tools.

Maintenance

ActivityActive
ResponsivenessResponsive