Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Desearch

NPM · DESEARCH-MCP-SERVER · 2 COMPONENTS · SCANNED OCT 2

AI search, X search, web search, page extraction, and X trends.

Available components

remote · mcp.desearch.ai 36 npm · desearch-mcp-server 49
49 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Desearch-ai/mcp-desearch). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Desearch MCP server?

Desearch runs locally as an npm package, launched with npx -y desearch-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · desearch-mcp-server

# add to Claude Code
claude mcp add desearch-ai-mcp-desearch -- npx -y desearch-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "desearch-ai-mcp-desearch": {
      "command": "npx",
      "args": [
        "-y",
        "desearch-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "desearch-ai-mcp-desearch": {
      "command": "npx",
      "args": [
        "-y",
        "desearch-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add desearch-ai-mcp-desearch -- npx -y desearch-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "desearch-ai-mcp-desearch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "desearch-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add desearch-ai-mcp-desearch --command npx --arg -y --arg desearch-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  desearch-ai-mcp-desearch:
    command: "npx"
    args: ["-y", "desearch-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "desearch-ai-mcp-desearch": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "desearch-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add desearch-ai-mcp-desearch -t stdio -c npx -a -y desearch-mcp-server
// mcp.json
{
  "mcpServers": {
    "desearch-ai-mcp-desearch": {
      "command": "npx",
      "args": [
        "-y",
        "desearch-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Oct 26 34

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 2 Oct 2026 · Analysed npm/desearch-mcp-server@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Desearch-ai/mcp-desearch
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Desearch-ai/mcp-desearch/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3036020526
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:db0d7789e87fa08cf1602798088722bb7898ce6aa1875e0293e339f0eb8cbedd837503fa1051b509bd40763d9d0e551ed360c19e96e35b2a2afbff15a

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Desearch MCP server?

Desearch is an MCP server listed in the public MCP registry as io.github.Desearch-ai/mcp-desearch. AI search, X search, web search, page extraction, and X trends. This page covers its npm package (desearch-mcp-server).

Is the Desearch MCP server safe to use?

Desearch scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

Is the Desearch MCP server still maintained?

Desearch is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Desearch MCP server under?

Desearch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.