io.github.Abidit/phi-guard-mcp
NPM · PHI-GUARD-MCP · SCANNED SEP 20
Local-first PHI detection for source code, LLM prompts, logs, and analytics
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 184 tokens (~92/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the io.github.Abidit/phi-guard-mcp server?
io.github.Abidit/phi-guard-mcp runs locally as an npm package, launched with npx -y phi-guard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · phi-guard-mcp
claude mcp add abidit-phi-guard-mcp -- npx -y phi-guard-mcp
{
"mcpServers": {
"abidit-phi-guard-mcp": {
"command": "npx",
"args": [
"-y",
"phi-guard-mcp"
]
}
}
} {
"servers": {
"abidit-phi-guard-mcp": {
"command": "npx",
"args": [
"-y",
"phi-guard-mcp"
]
}
}
} codex mcp add abidit-phi-guard-mcp -- npx -y phi-guard-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"abidit-phi-guard-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"phi-guard-mcp"
],
"enabled": true
}
}
} openclaw mcp add abidit-phi-guard-mcp --command npx --arg -y --arg phi-guard-mcp
mcp_servers:
abidit-phi-guard-mcp:
command: "npx"
args: ["-y", "phi-guard-mcp"] {
"McpServers": {
"abidit-phi-guard-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"phi-guard-mcp"
]
}
}
} assistant mcp add abidit-phi-guard-mcp -t stdio -c npx -a -y phi-guard-mcp
{
"mcpServers": {
"abidit-phi-guard-mcp": {
"command": "npx",
"args": [
"-y",
"phi-guard-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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.60 → unverified ▼ security
- Schema quality: 77 → 92 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.4 → 0.2.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 2026 · Analysed npm/phi-guard-mcp@0.2.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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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_suggest ~90
Given a raw text snippet (a log line, a prompt, an error message), detect PHI-shaped values and return a redacted version.
| Name | Type | Req | Description |
|---|---|---|---|
| includeMatchedValues | boolean | – | Echo the raw matched PHI values and the original text back in the result. Off by default: the result flows into the calling model's context. |
| text | string | yes | Raw text that may contain PHI |
No output schema declared.
No examples provided.
scan_code ~94
Scan a local directory of source files for sensitive identifiers (patient, diagnosis, dob, ssn, mrn, birthdate, medicalrecord) flowing into risky sinks (LLM calls, logging, analytics) before they ship.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the directory or repo to scan. A relative path is resolved against the server process's working directory, which an MCP client controls — prefer an absolute path. |
No output schema declared.
No examples provided.
What is the io.github.Abidit/phi-guard-mcp server?
io.github.Abidit/phi-guard-mcp is listed in the public MCP registry as io.github.Abidit/phi-guard-mcp. Local-first PHI detection for source code, LLM prompts, logs, and analytics. This page covers its npm package (phi-guard-mcp).
Is the io.github.Abidit/phi-guard-mcp server safe to use?
io.github.Abidit/phi-guard-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.Abidit/phi-guard-mcp server expose?
io.github.Abidit/phi-guard-mcp exposes 2 tools: redact_suggest, scan_code. Their descriptions and schemas cost roughly 184 tokens of context every time the server is loaded.
Is the io.github.Abidit/phi-guard-mcp server still maintained?
io.github.Abidit/phi-guard-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.Abidit/phi-guard-mcp server under?
io.github.Abidit/phi-guard-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.