# io.github.vladimirbakalov/secretguard-mcp (mcpb · secretguard-mcp-0.1.4.mcpb)

Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it.

- Trust score: 60/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `secretguard-mcp-0.1.4.mcpb`: 60/100 (this document), [markdown](https://verifymcp.io/servers/vladimirbakalov-secretguard-mcp/https-github-com-vladimirbakalov-secretguard-mcp-releases-download-v0-1-4-mcpb-s.md), [page](https://verifymcp.io/servers/vladimirbakalov-secretguard-mcp/https-github-com-vladimirbakalov-secretguard-mcp-releases-download-v0-1-4-mcpb-s)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/vladimirbakalov/secretguard-mcp/releases/download/v0.1.4-mcpb/secretguard-mcp-0.1.4.mcpb`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 37 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 192 tokens (~192/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

- Download bundle: `https://github.com/vladimirbakalov/secretguard-mcp/releases/download/v0.1.4-mcpb/secretguard-mcp-0.1.4.mcpb`

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 60, −3)

- [functional] Stability: pass → 0.77

### 2026-09-19 (score 63, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 61, −2)

- [functional] Stability: pass → 0.80

### 2026-09-12 (score 63, 0)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `scan_for_secrets` (~192 tokens)

Scan for secrets

Scans a code string for hardcoded secrets (AWS keys, Stripe keys, GitHub tokens, Google API keys, Slack tokens, private key blocks, JWTs, and generic high-entropy credentials assigned to secret/token/password/key-like variable names) BEFORE that code is written to a file or committed. Call this proactively whenever you are about to write, edit, or commit code that could plausibly contain a credential — config files, env handling, API client setup, tests with fixture values, or any snippet you're not 100% sure is clean — and again right before creating a commit or PR. Every reported line is redacted; the raw secret value is never returned.

Input parameters:

- `code` (string, required): The code to scan, as plain text (one file's contents, or any snippet).
- `filename` (string): Optional filename to attribute findings to (for display only). Defaults to "input".

Output parameters:

- `findings` (array)
- `summary` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vladimirbakalov-secretguard-mcp/https-github-com-vladimirbakalov-secretguard-mcp-releases-download-v0-1-4-mcpb-s#diagnostics

## Score history

- 2026-09-20: 60
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 61
- 2026-09-13: 61
- 2026-09-12: 63
- 2026-09-11: 63
- 2026-09-10: 62
- 2026-09-09: 62
- 2026-09-08: 62
- 2026-09-07: 61
- 2026-09-06: 61
- 2026-09-05: 60
- 2026-09-04: 60
- 2026-09-03: 59
- 2026-09-02: 59
- 2026-09-01: 58
- 2026-08-31: 58
- 2026-08-30: 57
- 2026-08-29: 57
- 2026-08-28: 56
- 2026-08-27: 56
- 2026-08-26: 55
- 2026-08-25: 54
- 2026-08-24: 54
- 2026-08-23: 53
- 2026-08-22: 53

## Common questions

### What is the io.github.vladimirbakalov/secretguard-mcp server?

io.github.vladimirbakalov/secretguard-mcp is listed in the public MCP registry as io.github.vladimirbakalov/secretguard-mcp. Scans code for hardcoded secrets (AWS, Stripe, GitHub, JWTs) before an AI agent commits it. This page covers its MCPB bundle (https://github.com/vladimirbakalov/secretguard-mcp/releases/download/v0.1.4-mcpb/secretguard-mcp-0.1.4.mcpb).

### Is the io.github.vladimirbakalov/secretguard-mcp server safe to use?

io.github.vladimirbakalov/secretguard-mcp scores 60 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 io.github.vladimirbakalov/secretguard-mcp server expose?

io.github.vladimirbakalov/secretguard-mcp exposes 1 tool: scan_for_secrets. Their descriptions and schemas cost roughly 192 tokens of context every time the server is loaded.

### What licence is the io.github.vladimirbakalov/secretguard-mcp server under?

io.github.vladimirbakalov/secretguard-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/vladimirbakalov/secretguard-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vladimirbakalov-secretguard-mcp/https-github-com-vladimirbakalov-secretguard-mcp-releases-download-v0-1-4-mcpb-s.xml
- Changelog JSON feed: https://verifymcp.io/servers/vladimirbakalov-secretguard-mcp/https-github-com-vladimirbakalov-secretguard-mcp-releases-download-v0-1-4-mcpb-s.json
- HTML version of this page: https://verifymcp.io/servers/vladimirbakalov-secretguard-mcp/https-github-com-vladimirbakalov-secretguard-mcp-releases-download-v0-1-4-mcpb-s