Skip to main content
Glama
telly6

searchpin

Related Servers

Alternatives to searchpin

Related Servers

  • A
    license
    A
    quality
    C
    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
  • A
    license
    A
    quality
    F
    maintenance
    Free multi-source web search server for AI agents, with confidence scoring and token optimization.
    3
    193 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    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.
    6
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI clients to run keyless web searches by aggregating nine domestic Chinese engines directly plus foreign engines through a self-maintained free node pool, with authority-weighted fusion, deduplication, and content fetching. Also provides deep research, engine health, proxy status, node pool management, and cache tools, all configurable from a built-in web panel.
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Self-hosted web search and page extraction for AI agents. Stdio MCP server, HTTP API and Python/npm CLI.
    8
    40 npm
    51 PyPI
    2
    MIT
  • A
    license
    A
    quality
    F
    maintenance
    Web search for AI agents across 6 engines (Serper, Brave, Exa, Tavily, Firecrawl, Perplexity) through one search tool. Routes each query to the cheapest engine that clears a quality bar and caches repeats. Hosted, streamable-HTTP, BYOK supported.
    1
    1
    MIT

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: web_search discovers ranked results, while web_fetch retrieves and extracts full page content. The descriptions explicitly direct the agent to use search first and fetch selected URLs afterward, so there is no realistic misselection.

Naming Consistency5/5

Both tool names follow the same web_<verb> convention: web_search and web_fetch. The pattern is predictable and clearly describes each operation.

Tool Count4/5

Only two tools are provided, but they are the essential primitives for this server's retrieval purpose. It is slightly under the typical 3-15 range, though the narrow search-and-fetch scope makes the minimal surface reasonable.

Completeness4/5

The core lifecycle of web information retrieval is covered: search for candidate URLs and fetch full text from chosen URLs. Minor gaps exist, such as batch fetching or richer search controls, but agents can work around these by iterating.

Maintenance

ActivityMaintained
ResponsivenessNo issues