Shadowgate Mcp
Scan MCP tool calls for prompt injection, leaked secrets, and risky patterns before agents touch production integrations.
Overview
io.github.josephibra/shadowgate-mcp is an MCP server for the Ship phase that firewalls agent MCP calls by scanning for injection, secrets, and security risks.
What is this MCP server?
- Firewall layer over MCP requests and responses
- Detection focus: injection, secrets exposure, risky content
- Hosted streamable-http remote at shadowgate-mcp.mcp.xpay.sh
- Version 1.0.0 from josephibra/shadowgate-mcp
- Complements agent tooling rather than replacing secure coding
- Server version 1.0.0
- 1 published streamable-http remote endpoint
- GitHub repository josephibra/shadowgate-mcp
What problem does it solve?
Every new MCP server increases the chance agents execute injected instructions or exfiltrate secrets through tool I/O.
Who is it for?
Indie builders running multiple MCP integrations who want an explicit security scan on agent tool traffic before launch.
Skip if: Teams without MCP in production, or organizations that need on-prem only with no hosted security remote.
What do I get? / Deliverables
Risky MCP traffic gets flagged or blocked so you can ship agent features with a dedicated security gate in the loop.
- Scanned MCP call pipeline with risk signals on injection and secrets
- Clearer go/no-go before enabling new tools in production
- Documented security gate in your agent launch checklist
Recommended MCP Servers
Journey fit
How it compares
MCP traffic firewall, not a full SAST suite or generic code-review skill.
Common Questions / FAQ
Who is io.github.josephibra/shadowgate-mcp for?
Solo builders and small teams shipping Claude Code or Cursor workflows with several MCP servers who want injection and secret scanning on tool calls.
When should I use io.github.josephibra/shadowgate-mcp?
Use it in Ship security when agent MCP usage is real, integrations are multiplying, and you need a policy layer before users or production data are exposed.
How do I add io.github.josephibra/shadowgate-mcp to my agent?
Register the remote MCP URL https://shadowgate-mcp.mcp.xpay.sh/mcp as streamable-http in your agent, place it according to your vendor’s firewall or proxy pattern, and test with benign and adversarial MCP payloads.