Skip to main content
Glama
Vybe-Finance

fetch-url-mcp

by Vybe-Finance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to fetch-url-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • web-scraper-mcp

      acceptancestronk01-sudo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to scrape and extract content from any public webpage, returning text, markdown, HTML, or structured JSON, with support for CSS selectors, metadata extraction, and x402 micropayments.
      6 npm
      MIT

    • MCP Web Fetch Server

      keroger2k
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables fetching content from any URL with support for different HTTP methods, custom headers, and request bodies. Designed to work with ChatGPT and other AI assistants for web scraping and API interactions.
      -
    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

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinguished by output type and use case: one returns readable plain text, the other pretty-printed JSON. The names themselves signal the difference, so there is minimal risk of selecting the wrong tool.

    Naming Consistency5/5

    Both tool names follow the same verb_noun snake_case pattern: fetch_url and fetch_json. The naming is predictable, concise, and exactly matches each tool's function.

    Tool Count4/5

    Two tools is slightly below the typical 3-15 range, but for the narrow purpose of fetching public URLs, the count is reasonable. Each tool earns its place, and adding more would likely inflate the surface unnecessarily.

    Completeness4/5

    The tool set covers the two most common URL-fetching needs: human-readable content and JSON APIs. It lacks support for binary content or raw HTML, but that appears beyond the server's stated scope, so the coverage is adequate with only minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources