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.

io.github.Dave-London/search

NPM · @PARETOOLS/SEARCH · SCANNED SEP 20

MCP server for code search (ripgrep + fd) with structured, token-efficient output

Available components

0 this week 94 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 & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Dave-London/Pare). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 31 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 498 tokens (~166/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.Dave-London/search MCP server?

io.github.Dave-London/search runs locally as an npm package, launched with npx -y @paretools/search. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @paretools/search

# add to Claude Code
claude mcp add dave-london-search -- npx -y @paretools/search
// .cursor/mcp.json
{
  "mcpServers": {
    "dave-london-search": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/search"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dave-london-search": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/search"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dave-london-search -- npx -y @paretools/search
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dave-london-search": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@paretools/search"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dave-london-search --command npx --arg -y --arg @paretools/search
# ~/.hermes/config.yaml
mcp_servers:
  dave-london-search:
    command: "npx"
    args: ["-y", "@paretools/search"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dave-london-search": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@paretools/search"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dave-london-search -t stdio -c npx -a -y @paretools/search
// mcp.json
{
  "mcpServers": {
    "dave-london-search": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/search"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 2026 · Analysed npm/@paretools/search@0.7.1

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 Dave-London/Pare
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Dave-London/Pare/.github/workflows/release.yml@refs/heads/main
Rekor log index 949169085
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:523de6945df179033dc8d73fa934312cb85852a8e824fb4a450b997e85507cd166d804f799fe916b27f0896e72b2df659422b3844ba4403b740809e6e

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 · 3 exposed · ~457 tokens

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 →

Tool Tokens
count ~138

Counts pattern matches per file using ripgrep. Returns per-file match counts and totals. Use instead of running `rg --count` or `grep -c` in the terminal.

NameTypeReqDescription
caseSensitivebooleanCase-sensitive search (default: true)
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
globstringGlob pattern to filter files (e.g., '*.ts', '*.{js,jsx}')
pathstringDirectory or file to search in (default: cwd)
patternstringyesRegular expression pattern to count matches for
NameTypeReqDescription
filesarrayyes
totalFilesnumberyes
totalMatchesnumberyes

No examples provided.

find ~155

Finds files and directories using fd with structured output. Returns file paths, names, and extensions. Use instead of running `fd` or `find` in the terminal.

NameTypeReqDescription
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
extensionstringFilter by file extension (e.g., 'ts', 'js')
maxResultsnumberMaximum number of results to return (default: 1000)
pathstringDirectory to search in (default: cwd)
patternstringRegex pattern to match file/directory names
typestringFilter by entry type: file, directory, or symlink
NameTypeReqDescription
filesarrayyes
totalnumberyes

No examples provided.

search ~164

Searches file contents using ripgrep with structured JSON output. Returns match locations with file, line, column, matched text, and line content. Use instead of running `rg` or `grep` in the terminal.

NameTypeReqDescription
caseSensitivebooleanCase-sensitive search (default: true)
compactbooleanAuto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
globstringGlob pattern to filter files (e.g., '*.ts', '*.{js,jsx}')
maxResultsnumberMaximum number of matches to return (default: 1000)
pathstringDirectory or file to search in (default: cwd)
patternstringyesRegular expression pattern to search for
NameTypeReqDescription
filesSearchednumberyes
matchesarrayyes
totalMatchesnumberyes

No examples provided.

Common questions

What is the io.github.Dave-London/search MCP server?

io.github.Dave-London/search is an MCP server listed in the public MCP registry as io.github.Dave-London/search. MCP server for code search (ripgrep + fd) with structured, token-efficient output. This page covers its npm package (@paretools/search).

Is the io.github.Dave-London/search MCP server safe to use?

io.github.Dave-London/search scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.

What tools does the io.github.Dave-London/search MCP server expose?

io.github.Dave-London/search exposes 3 tools: search, find, count. Their descriptions and schemas cost roughly 457 tokens of context every time the server is loaded.

Is the io.github.Dave-London/search MCP server still maintained?

io.github.Dave-London/search is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.Dave-London/search MCP server under?

io.github.Dave-London/search declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.