Skip to main content
Glama
VelvetSP

io.github.VelvetSP/web-retrieval-mcp

by VelvetSP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.VelvetSP/web-retrieval-mcp

No user-submitted related servers found.

    Related Servers

    • Groundlane

      lanefoundry
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents controlled access to the web, offering unified tools for fetching pages as Markdown, searching across multiple providers, and extracting structured data via CSS selectors.
      Apache 2.0
    • Wick by wickproject

      Wickofficial

      wickproject
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides browser-grade web access for AI agents, using Chrome's actual network stack to bypass anti-bot protections and return clean markdown.
      9
      -

    • myscrape

      Bonifatius94
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-contained web-research MCP server that lets local LLM agents search, fetch, and synthesize web content using tools like web_search, web_fetch, and web_research.
      2
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct retrieval surface: general web search, single-page fetch, arXiv paper search, single-paper inspection, related-paper expansion, and developer-index search. Potential overlaps are explicitly separated by corpus and use case, so an agent can reliably pick the right tool.

    Naming Consistency4/5

    All names are lowercase snake_case and grouped by domain (web_* and research_*), which makes them predictable. The minor inconsistency is that web_search/web_fetch are verb-object names, while the research_* tools are object-oriented and do not encode an action as clearly.

    Tool Count5/5

    Six tools is well-scoped for a retrieval server: two general web operations plus a four-tool research cluster. Each tool has a distinct responsibility, and there are no redundant or filler tools.

    Completeness5/5

    The surface covers general web search, full-page fetching, scholarly paper search, single-paper verification, related-paper exploration, and developer-source search. These cover the main retrieval workflows one would expect, with no obvious dead ends or missing core operations.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources