io.github.rudraneel93/mcp-guardian

MCPcommunity
v2.3.21io.github.rudraneel93UnknownUpdated 4mo agonpmGitHub

Security, cost, and health governance proxy for MCP infrastructure

A safety layer between your AI assistant and the tools it uses. Version 4.1.8 · Website · npm · Install & troubleshooting · Changelog Incident policy workflow — Enterprise AI investigation drawer can generate, preview, accept, or reject blocking rules from incidents npm publish hardening — ordered publish script with registry dep resolution checks and clean-install verification before server goes…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3GitHub stars
1Forks
4mo agoLast update
Package
Authorio.github.rudraneel93
LicenseUnknown
Version2.3.21
Sourcemcp-registry
npm@mcp-guardian/server
GitHubrudraneel93/mcp-guardian
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv4.1.8 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable3mo ago

The published package tarball could not be read at scan time (tarball exceeds 15MB cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

A safety layer between your AI assistant and the tools it uses. Version 4.1.8 · Website · npm · Install & troubleshooting · Changelog Incident policy workflow — Enterprise AI investigation drawer can generate, preview, accept, or reject blocking rules from incidents npm publish hardening — ordered publish script with registry dep resolution checks and clean-install verification before server goes live Dashboard stability — fix React hooks ordering in Security/Health panels that caused error…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.