Skip to main content
Glama
mnm-matin

captain-search

by mnm-matin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to captain-search

No user-submitted related servers found.

    Related Servers

    • Web Researcher MCP

      zoharbabin
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AI-powered web research — search (Google, Brave, Serper, SearXNG), scrape any page, extract PDFs/DOCX/YouTube transcripts, academic & patent search. Single Go binary. Works with Claude, Cursor, Copilot, and any MCP client.
      25
      58
      MIT

    • open-search-mcp

      rockindahizzy
      A
      license
      Not graded
      quality
      D
      maintenance
      Web search, page fetching, and research from the terminal or any MCP client — no API key required.
      1
      MIT

    • SearchForge

      divyanshu-iitian
      A
      license
      A
      quality
      A
      maintenance
      Free, open-source web search gateway and MCP server for LLMs, AI agents, and RAG. It provides no-key web, code, academic, and community search with deduplication, ranking fusion, and citation-ready results.
      3
      2
      MIT

    • Agent Search

      cedarsaam
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted, MCP-native web-search backend for AI agents that provides meta-search, clean extraction, RAG with citations, and GitHub project selection.
      3
      MIT

    • wigolo

      CraftArt
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform local-first web search, fetch, crawl, extract, cache, research, and autonomous information gathering through MCP, with no API keys or cloud dependencies.
      839 npm
      AGPL 3.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

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: web search, code search, and fetching a specific URL. There is no overlap between the tools, so an agent can easily select the correct one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores: search_web, fetch_webpage, search_code. This makes the tool set predictable and easy to navigate.

    Tool Count4/5

    Three tools is slightly minimal for a search-focused server, but it covers the core operations of web search, code search, and page fetching. The count is reasonable for a niche tool set.

    Completeness4/5

    The tool set covers the primary search and fetch workflows, but it lacks options like image or news search. Minor gaps exist, but agents can accomplish most tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources