Secret Scan
MCPB · MCP-SECRET-SCAN-1.0.0.MCPB · SCANNED SEP 21
Check text for leaked credentials before an agent writes or commits it. Runs locally.
Available components
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 Security13
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 134 tokens (~134/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · mcp-secret-scan-1.0.0.mcpb
Download bundleEvery 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.
- 20 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 12 Sept 26 43
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 21 Sept 2026 · Analysed mcpb/https://github.com/agentic-income-bot/mcp-secret-scan/releases/download/v1.0.0/mcp-secret-scan-1.0.0.mcpb@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
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 →
scan_for_secrets ~134
Scan text (a diff, file contents, or a proposed commit) for leaked credentials before writing or committing it. Detects AWS keys, GitHub tokens, Anthropic/OpenAI keys, Slack tokens, Stripe live keys, Google API keys, PEM private keys, EVM wallet private keys and BIP39 seed phrases. Runs locally; nothing is sent anywhere. Precision-first: no entropy heuristics, so commit SHAs and lockfile hashes do not trigger it.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text to scan. |
| filename | string | – | Optional filename, so sensitive names like .env are flagged too. |
No output schema declared.
No examples provided.
What is the Secret Scan MCP server?
Secret Scan is an MCP server listed in the public MCP registry as io.github.agentic-income-bot/mcp-secret-scan. Check text for leaked credentials before an agent writes or commits it. Runs locally. This page covers its MCPB bundle (https://github.com/agentic-income-bot/mcp-secret-scan/releases/download/v1.0.0/mcp-secret-scan-1.0.0.mcpb).
Is the Secret Scan MCP server safe to use?
Secret Scan scores 47 out of 100 on VerifyMCP. 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 Secret Scan MCP server expose?
Secret Scan exposes 1 tool: scan_for_secrets. Their descriptions and schemas cost roughly 134 tokens of context every time the server is loaded.
What licence is the Secret Scan MCP server under?
Secret Scan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.