Ghosthunt runs on your own machine — the client starts it, so there is no endpoint to ping. 48 installs a week from npm. Last commit 31 May 2026.
Find every leaked secret on your machine — API keys in .env files, shell history, and configs.
What the code does
We read the source, 5 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.
npm_config: "npm Config (.npmrc)",
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 ghosthunt -e 'YOUR_API_KEY=<YOUR_API_KEY>' -- npx -y ghosthunt{
"mcpServers": {
"ghosthunt": {
"command": "npx",
"args": [
"-y",
"ghosthunt"
],
"env": {
"YOUR_API_KEY": "<YOUR_API_KEY>"
}
}
}
}[mcp_servers.ghosthunt]
command = "npx"
args = ["-y", "ghosthunt"]
env = { YOUR_API_KEY = "<YOUR_API_KEY>" }{
"mcpServers": {
"ghosthunt": {
"command": "npx",
"args": [
"-y",
"ghosthunt"
],
"env": {
"YOUR_API_KEY": "<YOUR_API_KEY>"
}
}
}
}{
"servers": {
"ghosthunt": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ghosthunt"
],
"env": {
"YOUR_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Put your own value in place of
<YOUR_API_KEY> (Your API key for the service).
The author’s registry entry marks it as required.
Alternatives to Ghosthunt
same job, measured the same wayScans files for leaked secrets and API keys
Scans files for leaked secrets and API keys
Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.
Use API keys from your Keyfold vault in commands and .env files. No tool returns a secret value.
GitHub Secret Scanner - Find Leaked API Keys | Gitleaks
Run commands on your remote test machines over SSH without the agent ever seeing a secret.
Local secret guardrails: scan code, git changes and MCP configs for API keys; redact text
Detects leaked secrets (API keys, tokens, private keys) in source code.
Ghosthunt — questions
Answers built from our own checks of this server.