/

Companies / Bouncer / Subprocessors

Bouncer subprocessors

bouncer.run

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.

Classified asAI and machine learningCybersecurityDeveloper tools

The Bouncer homepage

Subprocessors of Bouncer

Bouncer declares 6 subprocessors.

From the company's own list.Read the source
SubprocessorPurposeLocationFirst seen
CloudflareFedRAMP registryEdge hosting, CDN, TLS termination and DDoS protection for bouncer.runGlobal edge network8 Nov 2026
Google (Sign in with Google)Optional identity provider for account sign-inGlobal8 Nov 2026
Lovable Cloud (Supabase)Database, authentication and file storage for accounts, agents, policies, call logs and scan reportsEuropean Union8 Nov 2026
SentryError monitoring so broken pages and failed requests can be diagnosedEuropean Union8 Nov 2026
npm registry, OSV.dev and the MCP servers you checkSources queried when you run a Security Check on a package or serverGlobal8 Nov 2026
x402 facilitator (x402.org)Settlement of optional per-call USDC payments between caller and API ownerGlobal / public blockchain8 Nov 2026

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