Skip to main content
Glama
telly6

searchpin

by telly6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to searchpin

Related Servers

  • 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 MCP

    lennney
    A
    license
    A
    quality
    F
    maintenance
    Free multi-source web search server for AI agents, with confidence scoring and token optimization.
    3
    56 npm
    Apache 2.0

  • 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

  • GroundRoute

    PROJECT-B-26
    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

  • Argus

    Khamel83
    A
    license
    B
    quality
    A
    maintenance
    One endpoint, five search providers. Search broker for AI agents with automatic fallback, RRF ranking, and budget enforcement. The LiteLLM of web search.
    13
    5
    MIT

  • local-search-gateway-mcp

    fleixweb
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides a free, no-paid-API web search gateway for AI agents using DuckDuckGo and Bing HTML scrapers, with tools for search, URL fetching, and text extraction.
    MIT
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.7/5.0

Scored across 2 tools

Disambiguation5/5

web_search and web_fetch have clearly distinct purposes: one handles query-based web search, the other fetches and extracts content from specific URLs. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern in snake_case: web_search, web_fetch. The naming is predictable and clear.

Tool Count4/5

With only 2 tools, the server is minimal but appropriate for its focused search-and-fetch domain. The count is not excessive, though a few more specialized search utilities could be added.

Completeness4/5

The server covers the essential search and fetch operations. The extensive instructions compensate for missing advanced features, but minor gaps like image search exist.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources