# DarkSearch.xyz (remote · www.darksearch.xyz)

Full-text search over web pages published on IPFS. Free, no key.

- Trust score: 39/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.darksearch.xyz`: 39/100 (this document), [markdown](https://verifymcp.io/servers/xyz-darksearch-search/www.md), [page](https://verifymcp.io/servers/xyz-darksearch-search/www)

## Channel facts

- Endpoint: `https://www.darksearch.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the DarkSearch.xyz MCP server?

DarkSearch.xyz is a hosted endpoint at https://www.darksearch.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http xyz-darksearch-search 'https://www.darksearch.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-darksearch-search": {
      "url": "https://www.darksearch.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-darksearch-search": {
      "type": "http",
      "url": "https://www.darksearch.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-darksearch-search]
url = "https://www.darksearch.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-darksearch-search": {
      "type": "remote",
      "url": "https://www.darksearch.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-darksearch-search --url 'https://www.darksearch.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-darksearch-search:
    url: "https://www.darksearch.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-darksearch-search": {
      "Transport": "http",
      "Url": "https://www.darksearch.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-darksearch-search -t streamable-http -u 'https://www.darksearch.xyz/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 39, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified

### 2026-11-04 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-03 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-02 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-01 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-31 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-30 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-29 (score 39, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-darksearch-search/www#diagnostics

## Score history

- 2026-11-05: 39
- 2026-11-04: 39
- 2026-11-03: 39
- 2026-11-02: 39
- 2026-11-01: 39
- 2026-10-31: 39
- 2026-10-30: 39
- 2026-10-29: 39
- 2026-10-28: 39
- 2026-10-27: 39
- 2026-10-26: 39
- 2026-10-25: 39
- 2026-10-24: 39
- 2026-10-23: 39
- 2026-10-22: 39
- 2026-10-21: 39
- 2026-10-20: 39
- 2026-10-19: 39
- 2026-10-18: 39
- 2026-10-17: 39
- 2026-10-16: 39
- 2026-10-15: 39

## Common questions

### What is the DarkSearch.xyz MCP server?

DarkSearch.xyz is an MCP server listed in the public MCP registry as xyz.darksearch/search. Full-text search over web pages published on IPFS. Free, no key. This page covers its hosted endpoint (https://www.darksearch.xyz/mcp).

### Is the DarkSearch.xyz MCP server safe to use?

DarkSearch.xyz scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Does the DarkSearch.xyz MCP server require authentication?

Its publisher declares no required credentials for DarkSearch.xyz. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the DarkSearch.xyz MCP server still maintained?

DarkSearch.xyz is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.darksearch.xyz/mcp
- Website: https://www.darksearch.xyz/security.php#api
- Changelog RSS feed: https://verifymcp.io/servers/xyz-darksearch-search/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-darksearch-search/www.json
- HTML version of this page: https://verifymcp.io/servers/xyz-darksearch-search/www