3 findingsStatic scanned
Guardion
guardion · MCP server
Guardion applies one policy to three areas of agent use. A local proxy in front of an MCP server redacts PII and secrets on tool input and output, restoring values on the way back, and checks calls for prompt injection and tool poisoning. Runtime hooks in Claude Code observe or block prompts and tool use, and a Shadow AI scanner inventories AI apps, agents, MCP servers, skills and plugins on a device and reports what changed. The policy is set in the Guardion console, and by default calls pass through if the Guardion API cannot be reached.
Written by ooruby from the README of @guardion/guardion 0.4.3.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Redacts secrets and personal data before the model sees them, and shows which AI tools are installed on a machine and what has changed.
What you could do with it
- Wrap one MCP server in the proxy so secrets and personal data reach the model only as placeholders.
- Install the Claude Code hooks to observe or block risky sessions and tools.
- Scan a device for installed AI apps, agents, MCP servers, skills and plugins and see what has changed.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Agent runtime governance — DLP for MCP servers, runtime guardrails for coding agents, and device-wide Shadow AI discovery
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.4.3, the file with digest sha512-OALArjS18BDIZvd1YP/M9B+VryTAERuKt0klgK4YvG8b/7e6t77SeVbPqbIPPlp3hwOvslMsF0HxjLM1xflhww==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"guardion": {
"command": "npx",
"args": [
"-y",
"@guardion/guardion@0.4.3"
]
}
}
}Or run it directly.
npx -y @guardion/guardion@0.4.3Pinned to 0.4.3, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @guardion/guardion
- Version read
- 0.4.3
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/guardion-guardion)About this listing
- Kind
- MCP server
- Category
- Infrastructure
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-07
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.