Companies / Bouncer / Subprocessors
Bouncer checks npm packages and MCP servers for security issues before they are connected, and runs a gateway that enforces tool policies, rate limits and spend caps on AI agent tool calls. It serves developers and API owners who connect AI agents to MCP servers and APIs.
Summarized from its homepage on 8 Nov 2026.
Subprocessors of Bouncer
Bouncer declares 6 subprocessors.
From the company's own list.Read the source
| Subprocessor | Purpose |
|---|---|
| Edge hosting, CDN, TLS termination and DDoS protection for bouncer.run | |
| Optional identity provider for account sign-in | |
| Lovable Cloud (Supabase) | Database, authentication and file storage for accounts, agents, policies, call logs and scan reports |
| Error monitoring so broken pages and failed requests can be diagnosed | |
| npm registry, OSV.dev and the MCP servers you check | Sources queried when you run a Security Check on a package or server |
| x402 facilitator (x402.org) | Settlement of optional per-call USDC payments between caller and API owner |
Vendor's own statement, retrieved from the source URL on the date shown. StrataDB does not verify the underlying claim. Data sources.
See Bouncer's full stack
Every vendor with its source and date, and an alert when Bouncer adds or drops one. The same lookup works for any company.
- Every company and vendor, with its public source
- 100 API calls a month, plus MCP and the Chrome extension
- Work email only. No card, no sales call