Skip to content
Darksearch logo

Darksearch MCP server

Which servers in the official MCP registry are Darksearch's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to Darksearch

Whose server it is
  • Registry namexyz.darksearch/searchverified in the MCP registry

The registry name sits under darksearch.xyz. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools1
  • Server calls itselfdarksearch
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 7 ms.

Should an agent connect itNot proven either way yet
  • Its tools do find text across public IPFS pages, but not report objectionable content found in results.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "find text across public IPFS pages", the likely first call is search_ipfs.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-21
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer62 ms
  • Space in an agent's context≈ 131 tokensthe definitions of all its tools (1), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 1 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · find text across public IPFS pages
  • not sure · query search results through the API
  • cannot · report objectionable content found in results

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers1 tools · read 2026-10-21
  • search_ipfs

    Full-text search over web pages published on IPFS. Returns JSON {total, approximate, results: [{cid, title, excerpt, url}]} (approximate: total is an estimate), where url fetches the page from a public gateway. Free tier: at most 10…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "search": {
      "type": "http",
      "url": "https://www.darksearch.xyz/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http darksearch https://www.darksearch.xyz/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://www.darksearch.xyz/mcp as a custom connector in the settings.

OpenAPI spec

1 paths, read 2026-10-21. Open the spec ↗

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.