Skip to main content
Glama
Sanoy24

safe-fetch-mcp-server

by Sanoy24

Related Servers

Alternatives to safe-fetch-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.
      1
      70 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Safe, self-hosted MCP server for web grounding that fetches live pages through a stealth-patched Chrome and returns clean Markdown with provenance, preventing SSRF and blocks.
      4
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A zero-dependency MCP server that fetches any HTTP(S) URL and returns clean content as text, Markdown, raw HTML, or formatted JSON, with robots.txt compliance and SSRF protection.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI clients controlled access to a real headless browser with domain allowlisting, SSRF protection, per-session isolation, audit logging, and persistent cookies/state across restarts.
      6 npm
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      MCP server for safely reading public URLs for AI agents, providing tools to fetch, extract, cache, and inspect web content as evidence.
      15
      MIT
    • A
      license
      Not graded
      quality
      D
      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

    TDQS

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With a single tool there is no possibility of misselection; the tool's purpose (safe read-only URL fetch) is unambiguous and clearly stated in the description.

    Naming Consistency5/5

    The lone tool uses a clear verb_noun snake_case name (fetch_url) that matches its action and target resource, with no competing conventions to clash with.

    Tool Count4/5

    The server is deliberately narrow-purpose (safe fetching), and the single tool is feature-rich—paging, format selection, byte/char limits, structured errors—so it earns its place rather than feeling thin. A single tool is still minimal for a general-purpose server, but here it fits the scope.

    Completeness4/5

    The fetch lifecycle is well covered: paging via nextStartIndex, format choice, size controls, caching info, and a thorough error taxonomy. Minor gaps exist (e.g. no batch fetch or metadata-only/HEAD variant), but core read workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues