Repotector runs on your own machine — the client starts it, so there is no endpoint to ping. 87 installs a week from npm. Last commit 18 Jul 2026.
The repo guardian AI agents handshake with before they touch your code.
Nothing serious here today
Today is the operative word: we check Repotector 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 repotector -- npx -y repotector{
"mcpServers": {
"repotector": {
"command": "npx",
"args": [
"-y",
"repotector"
]
}
}
}[mcp_servers.repotector]
command = "npx"
args = ["-y", "repotector"]{
"mcpServers": {
"repotector": {
"command": "npx",
"args": [
"-y",
"repotector"
]
}
}
}{
"servers": {
"repotector": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"repotector"
]
}
}
}Alternatives to Repotector
same job, measured the same wayTently, the AI PR reviewer for GitHub: agents check team decisions before they write code.
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
Your coding agent asks the business logic of your repository and checks commits before they land
Security tools for your AI: scan, pentest, check headers, guard code and scan repos for secrets.
Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.
Linters check your code. Invigil checks whether your repo is legible — to newcomers and AI agents.
Hands CAPTCHAs, 2FA codes and approvals from your agent to your human with one tap.
Check budgets before AI spend, record what your code spends and read Solwyn costs.
Repotector — questions
Answers built from our own checks of this server.