Sub-processors
Last updated: June 30, 2026
To operate MCP Inspector, we use the third-party service providers ("sub-processors") below. Because the product is local-first, none of these providers receive the contents of the MCP traffic you capture — that data stays on your device (Free/Pro) or on infrastructure you control (Team/Enterprise).
| Sub-processor | Purpose | Data involved |
|---|---|---|
| Stripe | Payment processing & subscription billing | Name, email, billing/payment details (card data handled by Stripe; we never see it) |
| Supabase | License database & validation backend | Email, org name, hashed license key, machine fingerprint, tier/seat metadata, validation log |
| Cloudflare | Website/CDN, license API edge, DNS | Standard web request metadata; license validation requests |
| Backblaze B2 | Installer & update file hosting | Download requests for installers/updates |
| Resend | Transactional email (license-key delivery) | Email address, license key |
Changes to this list
We may add or replace sub-processors as the product evolves. When we make a material change, we will update this page and its "Last updated" date. Business customers under a Data Processing Addendum may request advance notice of new sub-processors and may object on reasonable data-protection grounds.
Contact
Questions about our sub-processors? Email mcpagentinspector@gmail.com.
Related: Privacy Policy · DPA · All legal documents