Skip to main content
Glama
searchpin

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
    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.
    5
    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
    B
    maintenance
    Self-hosted web search and page extraction for AI agents. Stdio MCP server, HTTP API and Python/npm CLI.
    8
    52 npm
    2
    MIT
  • A
    license
    A
    quality
    D
    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 occupy clearly separate stages of the retrieval loop: web_search returns ranked titles/URLs/snippets, web_fetch returns full page text for a specific URL. Descriptions explicitly link them (search results tell you which URLs to fetch), so an agent cannot mistake one for the other.

Naming Consistency5/5

Both names are lowercase snake_case with the same verb_noun shape (web_search, web_fetch) and share a 'web_' prefix, forming a tight, predictable pair. The naming directly mirrors the read/fetch distinction.

Tool Count4/5

Only two tools, but they are exactly the minimal complete pair for a web research server — search without fetch or fetch without search would be useless. It is thin enough that it sits just above the borderline band, and nothing superfluous is included.

Completeness4/5

Search + fetch covers the full discover-then-read lifecycle, and the descriptions handle recency, multi-engine fallback, and snippet-first triage. Minor gaps remain: no parameter surface documented for site/domain restriction, news/date-scoped variants, or a batch-multi-URL fetch, so some workflows require extra round trips.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues