Skip to main content
Glama
llmops-pro

l402-search-mcp

by llmops-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to l402-search-mcp

No user-submitted related servers found.

    Related Servers

    • giskard-search

      giskard09
      A
      license
      A
      quality
      C
      maintenance
      Pay-per-use semantic web search for AI agents. Powered by SearxNG, agents pay in sats via Lightning Network micropayments — no API keys required.
      5
      1
      Apache 2.0

    • fathom

      Sherminatrix
      F
      license
      Not graded
      quality
      B
      maintenance
      Pay-per-call web scrape, search, and map for AI agents. HTTP MCP at /.well-known/mcp. Settle in USDC on Base (x402) or RLUSD/XRP. No API key; provider keys stay on the server.
      -

    • infomesh

      dotnetpower
      A
      license
      Not graded
      quality
      C
      maintenance
      Fully decentralized P2P web search engine for LLMs. Crawls, indexes, and searches the web via a peer-to-peer network — no API key, no billing. Exposes 5 MCP tools: web_search, fetch_page, crawl_url, fact_check, and status.
      6
      MIT
    • entroute by entroute

      entrouteofficial

      entroute
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables web search for AI agents with pay-per-search in USDC, no API keys needed.
      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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: 'search' performs a paid query, while 'search_service_info' provides free metadata about the service. There is no overlap in functionality.

    Naming Consistency4/5

    Both tools start with 'search', but one is a single verb while the other is a compound noun. The pattern is mostly consistent, though not fully uniform.

    Tool Count3/5

    With only 2 tools, the surface is minimal. For the niche L402 search domain, it may be sufficient, but it feels slightly thin compared to typical integration scopes.

    Completeness3/5

    The set covers the core workflow: check service status and perform a paid search. However, missing features like invoice management or search history create minor gaps for advanced use cases.

    Resources