PreClone runs on your own machine — the client starts it, so there is no endpoint to ping. 24 installs a week from npm.
Check what a repo would run on your machine (open, agent start, install) before you clone it.
Nothing serious here today
Today is the operative word: we check PreClone every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add preclone -- npx -y preclone{
"mcpServers": {
"preclone": {
"command": "npx",
"args": [
"-y",
"preclone"
]
}
}
}[mcp_servers.preclone]
command = "npx"
args = ["-y", "preclone"]{
"mcpServers": {
"preclone": {
"command": "npx",
"args": [
"-y",
"preclone"
]
}
}
}{
"servers": {
"preclone": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"preclone"
]
}
}
}Alternatives to PreClone
same job, measured the same wayMake a coding agent prove it: run the repo's real tests, typecheck and lint before it says done.
Let your AI agents claim a task, work inside it and report back on your LatticeRun task tree.
Check whether a Claude Code skill was tested and whether it works before installing it.
Vet an agent skill before you install it: structure, triggers, secrets.
Check a Base or BNB Chain address before you pay it: on-chain risk reports, EAS attestations.
Which parts of what you want to build open source already covers. Every repo checked live.
Attention report for your open GitHub PRs: what needs you right now.
Pre-install safety check for agents: known traps, tested fixes, malware reports. No account.
PreClone — questions
Answers built from our own checks of this server.