io.github.MCPShield-Dev/mcpshield

MCPcommunity
v2.0.2io.github.MCPShield-DevUnknownUpdated 5mo agonpmGitHub

Security scanner for MCP servers - detects tool poisoning and injection

Scan MCP servers and GitHub repositories for security vulnerabilities. Powered by MCPShield — the MCP security scanner with 59+ detection rules covering the OWASP MCP Top 10. Get a free API key at mcpshield.co/settings, then: — Scan completed, no critical findings — Error (invalid key, rate limit, scan failure) — Scan completed with critical findings — API key (alternative to ) — Custom API…

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 →
5mo agoLast update
Package
Authorio.github.MCPShield-Dev
LicenseUnknown
Version2.0.2
Sourcemcp-registry
npmmcpshield-cli
GitHubMCPShield-Dev/mcpshield
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✓ 18 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv2.0.2 · 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

No tool declarations found in the source3mo ago

Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Scan MCP servers and GitHub repositories for security vulnerabilities. Powered by MCPShield — the MCP security scanner with 59+ detection rules covering the OWASP MCP Top 10. Get a free API key at mcpshield.co/settings, then: — Scan completed, no critical findings — Error (invalid key, rate limit, scan failure) — Scan completed with critical findings — API key (alternative to ) — Custom API endpoint (for self-hosted)

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.