Show HN: MCPShield – Supply chain security scanner for MCP servers
github.com
github.com
Thing is — your scanner catches the dumb mistakes (eval on untrusted input, hardcoded creds). Those devs are careless. The scarier category is servers with zero code vulns because they were written specifically to be malicious. Clean repo, good README, useful-sounding tool name. Passes every static check. Then on day 7 after it's in a thousand configs, the tool description quietly gets a new paragraph that the LLM reads as instructions.
You can't lint your way out of that. It's a trust problem not a code quality problem.
Does MCPShield do any post-install monitoring or is it purely a before you pull the trigger tool?
Typosquat packages that steal credentials (we found mcp-servr-github harvesting env vars) Known CVEs in Anthropic's own Git MCP server (CVE-2025-68145, RCE via prompt injection) Hardcoded database passwords visible to LLMs in tool metadata Agents with access to ~/.ssh and ~/.aws
The MCP ecosystem is following the same trajectory as npm/PyPI — rapid adoption with minimal vetting. 88% of orgs deploying AI agents have had security incidents. MCPShield scans your claude_desktop_config.json (or Cursor/VS Code config) and catches these before deployment. Zero dependencies, works offline, CI/CD-ready. We built this in the open because MCP security is a collective action problem. PRs and CVE reports welcome.