io.github.BasilSkyWalk/parecode
NPM · PARECODE · SCANNED SEP 20
Token-aware ripgrep code search and atomic multi-file edits for coding agents.
Available components
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 Security99
- 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 110 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 BasilSkyWalk/parecode). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 97 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 975 tokens (~325/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
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 3 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
How do I install the io.github.BasilSkyWalk/parecode MCP server?
io.github.BasilSkyWalk/parecode runs locally as an npm package, launched with npx -y parecode. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · parecode
claude mcp add basilskywalk-parecode -- npx -y parecode
{
"mcpServers": {
"basilskywalk-parecode": {
"command": "npx",
"args": [
"-y",
"parecode"
]
}
}
} {
"servers": {
"basilskywalk-parecode": {
"command": "npx",
"args": [
"-y",
"parecode"
]
}
}
} codex mcp add basilskywalk-parecode -- npx -y parecode
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"basilskywalk-parecode": {
"type": "local",
"command": [
"npx",
"-y",
"parecode"
],
"enabled": true
}
}
} openclaw mcp add basilskywalk-parecode --command npx --arg -y --arg parecode
mcp_servers:
basilskywalk-parecode:
command: "npx"
args: ["-y", "parecode"] {
"McpServers": {
"basilskywalk-parecode": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"parecode"
]
}
}
} assistant mcp add basilskywalk-parecode -t stdio -c npx -a -y parecode
{
"mcpServers": {
"basilskywalk-parecode": {
"command": "npx",
"args": [
"-y",
"parecode"
]
}
}
} 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.
- 20 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
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/parecode@0.7.0
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 | BasilSkyWalk/parecode |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/BasilSkyWalk/parecode/.github/workflows/release.yml@refs/tags/v0.7.0 |
| Rekor log index | 1775167646 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9c166e9a4a6dfd3fd586b35f95ee248bd0c1bf49b30de93123f3a6306056c59205167cb4b7dd2e90ec94488db1d27e864f83dcd5ec39ddaba105201cb |
Background: How many MCP packages publish verified provenance →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ParecodeEdit ~254
Apply many edits across many files in one call — the edit counterpart to ParecodeSearch/ParecodeExpand. Prefer over native Edit/MultiEdit for 2+ edits to one file, edits across files (files apply in parallel), or one logical revision that should land together. Each item is a line-range op (replaceLines or insertAfter, guarded by an `expect` anchor) or a string-patch op (oldString/newString; fuzzy:true tolerates whitespace drift, 'aggressive' also normalizes Unicode look-alikes). Strongly prefer line-range ops when you know the target lines — e.g. the line numbers ParecodeSearch returned: a line number plus a short `expect` anchor skips constructing exact-match snippets, so recurring text (a repeated call) can't trigger the multiple-match errors and retries an oldString needs extra context to avoid. Reserve oldString for edits with no known lines. Atomicity is per file, NOT cross-file: within a file all ops apply or none, other files commit independently — check each result's status. Writes are atomic with mtime conflict detection; fuzzy fails closed on low confidence or ambiguity.
| Name | Type | Req | Description |
|---|---|---|---|
| edits | array | yes | List of edit operations to perform |
No output schema declared.
No examples provided.
ParecodeExpand ~237
Read a specific line range of a file — the natural follow-up to a ParecodeSearch match or an `omittedLineRanges` entry it returned. Use instead of a full-file Read (or Read with offset/limit) when you already know roughly where the code lives and just need more lines around it. Give the known (file, startLine, endLine) and optionally pad with contextBefore/contextAfter; out-of-range lines are clamped silently and the returned `lineRange` reflects the actual slice. Reports `estimatedTokens` in the same form as ParecodeSearch so you can budget before consuming. Read-only — to change code use ParecodeEdit.
| Name | Type | Req | Description |
|---|---|---|---|
| contextAfter | number | – | Additional lines to include after endLine. Default 0. |
| contextBefore | number | – | Additional lines to include before startLine. Default 0. |
| endLine | number | yes | Ending line (1-based, inclusive) |
| file | string | yes | Path to the file to read (typically the `file` from a ParecodeSearch match). |
| startLine | number | yes | Starting line (1-based, inclusive) |
No output schema declared.
No examples provided.
ParecodeSearch ~484
Search the codebase with ripgrep and get matches plus surrounding context in ONE call — use instead of Grep/Glob-then-Read, a raw `rg`/`grep` in the shell, or re-reading the same file at different line ranges. Pass `pattern` as an array to run several regexes in parallel for flow tracing (e.g. ['HandleX','OnX','XClosed']); each match lists which `patterns` hit it. Overlapping or adjacent windows in a file are merged (gap ≤ contextLines), and the result carries one envelope-level `estimatedTokens` so you can budget before consuming. Read-only: to widen a match use ParecodeExpand, to change code use ParecodeEdit. Per-file content over ~2KB is dropped (its lines listed in `omittedLineRanges`) to protect context — widen those via ParecodeExpand instead of re-reading the file. Repeated calls in the same session are token-efficient: previously-returned windows return as `kind: 'reference'` placeholders. Watch the `warnings` field — a `pattern_directory_collision` almost always means narrow the pattern before retrying. Needs ripgrep on PATH (run `parecode doctor` if missing). In CodeGraph repos (.codegraph/), prefer codegraph_explore for broad 'how does X work?' questions; this stays best for targeted multi-pattern lookups.
| Name | Type | Req | Description |
|---|---|---|---|
| contextLines | number | – | Number of context lines to include around matches. Defaults to 2. Also controls window-merge threshold within a file. |
| maxBytesPerFile | number | – | Soft cap on bytes returned per file; above it, output is chunked around match centers and the trimmed lines are reported in omittedLineRanges (widen them with ParecodeExpand). |
| paths | array | – | Directory or file paths to restrict the search. Defaults to the current working directory. |
| pattern | – | yes | Ripgrep regex pattern, or an array of patterns to dispatch in parallel. Each match reports which input pattern(s) contributed via 'patterns'. |
| relatedSymbols | boolean | – | Opt-in: scan each match's content for likely related symbols (Handle<X>, On<X>, <X>Handler, <X>Listener, <X>Closed/Completed/Started). Returns deduped, lexically sorted, capped at 10 per match. |
No output schema declared.
No examples provided.
What is the io.github.BasilSkyWalk/parecode MCP server?
io.github.BasilSkyWalk/parecode is an MCP server listed in the public MCP registry as io.github.BasilSkyWalk/parecode. Token-aware ripgrep code search and atomic multi-file edits for coding agents. This page covers its npm package (parecode).
Is the io.github.BasilSkyWalk/parecode MCP server safe to use?
io.github.BasilSkyWalk/parecode scores 92 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.BasilSkyWalk/parecode MCP server expose?
io.github.BasilSkyWalk/parecode exposes 3 tools: ParecodeSearch, ParecodeEdit, ParecodeExpand. Their descriptions and schemas cost roughly 975 tokens of context every time the server is loaded.
Is the io.github.BasilSkyWalk/parecode MCP server still maintained?
io.github.BasilSkyWalk/parecode 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.BasilSkyWalk/parecode MCP server under?
io.github.BasilSkyWalk/parecode declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.