io.github.pamela-0/safe-fix-mcp
PYPI · SAFE-FIX-MCP · SCANNED AUG 20
Finds real dead code and proposes a safe, test-gated branch+PR to remove it.
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 →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 2 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 405 tokens (~202/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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (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.
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.
pypi · safe-fix-mcp
claude mcp add pamela-0-safe-fix-mcp -- uvx safe-fix-mcp
codex mcp add pamela-0-safe-fix-mcp -- uvx safe-fix-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pamela-0-safe-fix-mcp": {
"type": "local",
"command": [
"uvx",
"safe-fix-mcp"
],
"enabled": true
}
}
} openclaw mcp add pamela-0-safe-fix-mcp --command uvx --arg safe-fix-mcp
mcp_servers:
pamela-0-safe-fix-mcp:
command: "uvx"
args: ["safe-fix-mcp"] {
"mcpServers": {
"pamela-0-safe-fix-mcp": {
"command": "uvx",
"args": [
"safe-fix-mcp"
]
}
}
} 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.
- 20 Aug 26 63
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 20 Aug 2026 · Analysed pypi/safe-fix-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
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.
propose_removal_pr ~157
Propose a real branch+PR removing only unused imports (single-name import lines, >= 90% vulture confidence) from a Python repository. Runs the repo's own full test suite as a safety gate before ever committing or pushing — a failure there reverts everything and nothing is committed or pushed. If `gh` isn't available or PR creation otherwise fails, the branch is still committed and pushed for real; only the PR itself needs opening manually. A human always merges — this never merges anything itself. repo_path: path to a real git repository with a clean working tree (uncommitted changes are refused, not overwritten).
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_dead_code ~130
Scan a Python repository for real dead code (vulture) and dependency issues (deptry). Read-only — never modifies anything. Returns a human-readable list of findings, or "No real candidates found." repo_path: path to the repository to scan (must contain a pyproject.toml for the dependency checks to run; dead-code scanning works regardless). min_confidence: vulture's own confidence threshold (0-100). Lower values surface more candidates but more false positives.
| Name | Type | Req | Description |
|---|---|---|---|
| min_confidence | integer | – | – |
| repo_path | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.