LeakGuard
NPM · @AGENTGATE-BUILDER/LEAKGUARD · 2 COMPONENTS
Find and redact leaked secrets, wallet keys and PII before an AI agent sends text.
Available components
Last scanned (6 hours ago)
Scores higher than 28% of npm servers
Category Security
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 498 tokens (~249/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every 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.
- 22 Oct 26 46
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 22 Oct 2026 · Analysed npm/@agentgate-builder/leakguard@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
redact_text Redact secrets, wallet keys and PII from text ~137
Runs locally and offline. Same detection as scan_for_leaks, plus the redacted text ([REDACTED:type], or masked PII with style=mask) to send instead of the original.
| Name | Type | Req | Description |
|---|---|---|---|
| min_severity | string | – | – |
| style | string | – | label: [REDACTED:type] (default); mask: keep last 4 digits / email domain for PII |
| text | string | yes | Text your agent is about to send to an LLM, tool, log or webhook |
| types | array | – | Only these finding types or categories (wallet_key, secret, pii, email, ...) |
No output schema declared.
No examples provided.
scan_for_leaks Check text for leaked secrets before sending it ~246
Runs locally and offline. Finds crypto wallet keys (BIP39 seed phrases with checksum, EVM and Solana private keys, WIF, xprv), API secrets (GitHub, AWS, Stripe, OpenAI, Anthropic, Slack, Telegram, npm, JWT, PEM, credentialed URLs, password= assignments) and PII (cards, IBAN, SSN, email, phone, IP). Returns verdict (WALLET_KEY_EXPOSED / SECRETS_FOUND / PII_FOUND / CLEAN), safe_to_send and findings with masked previews (never the secret). Pattern and validator based detection: it can miss secrets in unknown formats and can flag look-alikes. A clean result is not a guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| min_severity | string | – | – |
| style | string | – | label: [REDACTED:type] (default); mask: keep last 4 digits / email domain for PII |
| text | string | yes | Text your agent is about to send to an LLM, tool, log or webhook |
| types | array | – | Only these finding types or categories (wallet_key, secret, pii, email, ...) |
No output schema declared.
No examples provided.
How do I install the LeakGuard MCP server?
LeakGuard runs locally as an npm package, launched with npx -y @agentgate-builder/leakguard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @agentgate-builder/leakguard
claude mcp add co-youraitools-leakguard -- npx -y @agentgate-builder/leakguard
What is the LeakGuard MCP server?
LeakGuard is an MCP server listed in the public MCP registry as co.youraitools/leakguard. Find and redact leaked secrets, wallet keys and PII before an AI agent sends text. This page covers its npm package (@agentgate-builder/leakguard).
Is the LeakGuard MCP server safe to use?
LeakGuard scores 46 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. 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 LeakGuard MCP server expose?
LeakGuard exposes 2 tools: scan_for_leaks, redact_text. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.
Is the LeakGuard MCP server still maintained?
LeakGuard is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the LeakGuard MCP server under?
LeakGuard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.