FinishKit runs on your own machine — the client starts it, so there is no endpoint to ping. 43 installs a week from npm. Last commit 30 Mar 2026.
FinishKit MCP: scan GitHub repos for security vulnerabilities, deployment blockers, and quality
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
execSync(`${check} ${cmd}`, { stdio: 'ignore' })
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
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 mcp -e 'FINISHKIT_API_KEY=<FINISHKIT_API_KEY>' -- npx -y @finishkit/mcp{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@finishkit/mcp"
],
"env": {
"FINISHKIT_API_KEY": "<FINISHKIT_API_KEY>"
}
}
}
}[mcp_servers.mcp]
command = "npx"
args = ["-y", "@finishkit/mcp"]
env = { FINISHKIT_API_KEY = "<FINISHKIT_API_KEY>" }{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@finishkit/mcp"
],
"env": {
"FINISHKIT_API_KEY": "<FINISHKIT_API_KEY>"
}
}
}
}{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@finishkit/mcp"
],
"env": {
"FINISHKIT_API_KEY": "<FINISHKIT_API_KEY>"
}
}
}
}Put your own value in place of
<FINISHKIT_API_KEY> (FinishKit API key (format: fk_live_...). Get one at finishkit.app/dashboard/settings).
The author’s registry entry marks it as required.
Alternatives to FinishKit
same job, measured the same wayMCP server that scans your repo's dependencies for security vulnerabilities based on published CVEs.
Scan a GitHub repository for vulnerabilities, with proof for every finding, from your coding agent.
Analyzes code for bugs, security vulnerabilities, and code smells
GitHub CI/CD MCP server with 70 tools for repos, PRs, Actions, deployments, billing, and more.
Vulnerability management: scan projects, search sealed packages, manage sealing rules and reports.
PQC scanner for GitHub repos and smart contracts. Detects quantum-vulnerable ECDSA/RSA.
Audit GitHub repos for malicious and supply-chain code before you depend on them.
Trigger security scans and read reports/vulnerabilities via the hosted Scannd API. Free: 2 scans/mo.
FinishKit — questions
Answers built from our own checks of this server.