Skip to main content
Glama
Sign In
YaCy Fork Peer-to-Peer Search

YaCy Fork Peer-to-Peer Search

by pad01g
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to YaCy Fork Peer-to-Peer Search

No user-submitted related servers found.

    Related Servers

    • keyless-web-search-mcp

      dollarser
      F
      license
      A
      quality
      C
      maintenance
      Enables keyless web search across multiple engines with fallback and relevance ranking, plus anonymous HTTP(S) page fetching, all without API keys or vendor dependencies.
      2
      1
      -

    • infomesh

      dotnetpower
      A
      license
      Not graded
      quality
      B
      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.
      8
      MIT

    • web-research-mcp

      wyzz973
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables keyless local web search and page fetching through MCP, with domain-filtered queries, extractable original-text evidence, hashes, and snapshot cursors for verifiable, traceable results.
      34 npm
      MIT

    • searxncrawl

      naoki760
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to run web searches across self-hosted SearXNG and/or You.com in parallel and to crawl single pages or whole sites into clean, deduplicated Markdown or JSON. It runs locally via STDIO or HTTP MCP transports, supports authenticated crawls, and requires no API key when using SearXNG.
      -

    • web-mcp

      panuhen
      A
      license
      A
      quality
      B
      maintenance
      Gives AI agents local web search and page reading with no API keys, layering a SearXNG-backed search cache with browser-based fallbacks and returning clean page text from HTML, PDF, JSON, and archived snapshots. Fetches run in Docker alongside the search engine with SSRF protection, egress filtering, and untrusted-content marking so agents can safely retrieve live web data.
      2
      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.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct action: search_web for querying, crawl_site/list_crawls/control_crawl for crawl lifecycle, get_index_status/list_peers for peer and index state, get/set_ranking_setting/evaluate_ranking for ranking, delete_document for index removal, and get_trust_status for trust. The only mild overlap between get_index_status and list_peers is resolved by descriptions (own peer vs other peers).

    Naming Consistency4/5

    All names use snake_case and a verb_noun pattern (get_ranking_settings, search_web, crawl_site, etc.). Minor inconsistency: get_ranking_settings uses plural 'settings' while set_ranking_setting uses singular 'setting'.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range and each tool has a clear, non-redundant role in the P2P search peer management workflow.

    Completeness4/5

    The surface covers the core lifecycle: search, crawl management, index deletion, peer status, ranking read/write/evaluate, and trust inspection. Gaps include no way to write trust statements (only read), no direct listing of indexed documents (only via search), and no peer connection management.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources