How a fintech startup secured their MCP tools in 30 minutes
Series A Fintech — London
Challenge
A fast-growing payments startup had integrated 12 MCP servers across their AI agent stack for everything from customer onboarding to fraud detection. During a routine sprint, a developer noticed API keys appearing in MCP tool responses — but had no way to audit the full surface area. With SOC 2 auditors arriving in 3 weeks, they needed answers fast.
Solution
We deployed MCPScan across their entire MCP configuration. Within 30 minutes, the scan completed all 10 check modules — uncovering 3 credential leaks in tool descriptions, 2 SSRF-vulnerable endpoints, and a toxic data flow where customer PII was being passed between tools without sanitisation. All findings were local-first with zero data leaving their infrastructure.
Results
- ✓3 credential leaks identified and remediated same day
- ✓2 SSRF vulnerabilities patched before production exposure
- ✓Toxic data flow between 4 tools mapped and isolated
- ✓SOC 2 audit passed on first attempt
- ✓MCPScan now runs in CI/CD on every MCP config change
“We thought our MCP setup was secure because each tool worked fine individually. MCPScan showed us the gaps between them — the toxic flows we couldn't see. It probably saved us from a breach.”
— Head of Engineering