Skip to main content
Glama
Sign In
fetchira

fetchira

by ImmuneFOMO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to fetchira

No user-submitted related servers found.

    Related Servers

    • polysearch-mcp

      mayigululu-hash
      A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates multiple search APIs behind a single web_search tool that automatically fails over to the next provider when quota runs out or a source breaks. Also exposes page fetching as Markdown and per-provider usage/circuit-breaker status.
      15 npm
      MIT

    • Free Internet Search Router

      mc-marcocheng
      A
      license
      Not graded
      quality
      C
      maintenance
      Pools multiple configured search provider API keys behind a single endpoint and exposes MCP tools for web search and document reading, enabling agents to keep searching when individual quotas are exhausted and fetch HTML/PDF content as Markdown.
      MIT

    • searchhub

      woodcoal
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to perform unified web searches across multiple search providers with automatic key rotation, failover, and circuit breaking, and to inspect provider status and capabilities.
      79 npm
      3
      MIT

    • FrankenSurf

      yail259
      A
      license
      Not graded
      quality
      B
      maintenance
      Read any web page and search the web for free. Routes each page across 28 web tools cheapest first (plain HTTP, Jina Reader, Chromium, stealth browsers) and checks it's the page you asked for before returning it. Paid tools stay off unless you add keys.
      710 PyPI
      110
      Apache 2.0
    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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target clearly different actions (search, deep_research, create_image, usage), but browser and read overlap heavily since both load a URL and return markdown. The read description's note that it auto-escalates to browser helps, but an agent could still reasonably pick either for a simple fetch.

    Naming Consistency3/5

    All names are lowercase snake_case and readable, but conventions are mixed: bare verbs (read, search), bare nouns (browser, usage), a verb_noun (create_image), and a compound (deep_research). No single predictable pattern guides naming.

    Tool Count5/5

    Six tools is well within a healthy range and each earns its place: fetching, searching, deep research, image generation, and quota inspection. No obvious filler or missing companion tool.

    Completeness4/5

    The surface covers the core domain well: URL fetch via read/browser, search, multi-source research, image generation/editing, and quota introspection. Minor gaps include no explicit batch/multi-URL crawl tool (only available via provider-specific modes) and no dedicated session or result management beyond opaque tokens.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources