Skip to content
Darksearch logo

Darksearch

Full-text search over public pages stored on IPFS, with a denylist filter and an API.
At a glanceswept Oct 15, 2026

≈ 2visits/mo

Little sign of use · estimate, read Oct 15, 2026

  • Darksearch2
  • #1 Exa183k
For
Security teams and people searching publicly published content on the IPFS network
Runs as
API
Used for
  • find text across public IPFS pages
  • query search results through the API
  • report objectionable content found in results
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 21, 2026
  • MCP serverxyz.darksearch/searchverified in the MCP registry
  • Stateanswers, 1 toolschecked 2026-10-21
  • Address to connectwww.darksearch.xyz/mcp
  • OpenAPI spec1 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Retrieval (RAG)by use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Darksearch with

Pick up to two.

All 10 alternatives to Darksearch →

All Retrieval (RAG) tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Darksearch for?

Sign in to leave a note
Questions this page answers
  • What is Darksearch?

    Full-text search over public pages stored on IPFS, with a denylist filter and an API. It is listed in the Atlas under Retrieval (RAG).

  • Who is Darksearch for?

    Security teams and people searching publicly published content on the IPFS network

  • Do people use Darksearch?

    Little sign of use: ≈ 2 visits/mo · estimate, 2026-10.

  • What are alternatives to Darksearch?

    In Retrieval (RAG), by use: Meilisearch, You.com, Zilliz, Jina AI, turbopuffer, Keenable.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk