PreClone
NPM · PRECLONE
Check what a repo would run on your machine (open, agent start, install) before you clone it.
Available components
Last scanned (3 hours ago)
Scores higher than 32% of npm servers
Category Security
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 532 tokens (~266/item across 2 items; 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 49
First indexed and scored.
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 5 Nov 2026 · Analysed npm/preclone@1.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_path Check a folder or archive on this machine ~175
Reads a folder, .zip, .tar.gz or .tgz on this machine and lists everything it would run, grouped by when: opening it in an editor, starting an AI agent in it, installing, running and committing. Static analysis only: nothing is run, and the files aren't uploaded anywhere. Use it on a downloaded project, a take-home assignment or a folder someone sent you before opening it, installing it or working in it. node_modules is skipped.
| Name | Type | Req | Description |
|---|---|---|---|
| offline | boolean | – | Skip the dependency lookups on npm and OSV. Default false. |
| path | string | yes | Absolute path to the folder or archive (~ is expanded). |
| time_limit_seconds | integer | – | Seconds to spend reading files (default 60). If it runs out, the report says the check is incomplete and what wasn't read. |
No output schema declared.
No examples provided.
check_repo Check a repository before cloning it ~245
Downloads a GitHub, GitLab or Bitbucket repository's archive and lists everything it would run on this machine, grouped by when: opening the folder in an editor, starting an AI agent in it (hooks, MCP servers, hidden instructions), installing, running and committing. Static analysis only: nothing from the repository is run. Use it before cloning, opening or installing a repository you didn't write, or before following its README's setup steps. Private repos use GITHUB_TOKEN or GITLAB_TOKEN from the server's environment.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch or tag to check. Defaults to the one in the URL, or the default branch. |
| offline | boolean | – | Skip the dependency lookups on npm and OSV. Default false. |
| repository | string | yes | A repository URL (https://github.com/owner/repo, a /tree/<branch> URL, gitlab.com or bitbucket.org), GitHub shorthand owner/repo, or a whole `git clone` line. |
| time_limit_seconds | integer | – | Seconds to spend reading files (default 60). If it runs out, the report says the check is incomplete and what wasn't read. |
No output schema declared.
No examples provided.
How do I install the PreClone MCP server?
PreClone runs locally as an npm package, launched with npx -y preclone. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · preclone
claude mcp add catsnotdrugs-preclone -- npx -y preclone
What is the PreClone MCP server?
PreClone is an MCP server listed in the public MCP registry as io.github.catsnotdrugs/preclone. Check what a repo would run on your machine (open, agent start, install) before you clone it. This page covers its npm package (preclone).
Is the PreClone MCP server safe to use?
PreClone scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 PreClone MCP server expose?
PreClone exposes 2 tools: check_repo, check_path. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.
Is the PreClone MCP server still maintained?
PreClone is still listed as active in the MCP registry. We last reached this channel on 5 November 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 PreClone MCP server under?
PreClone declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.