Skip to main content
Inflection is a multi-tenant marketing automation platform that includes a Model Context Protocol (MCP) endpoint at mcp.inflection.io, exposing your tenant’s marketing surface to AI assistants like Claude, ChatGPT, and Cursor. This page documents how we run that service, what data we handle, and how to reach us about security or support.

​
Deployment

  • Model: Multi-tenant SaaS, single global region.
  • Cloud: Amazon Web Services, US region.
  • Data plane: AWS-managed document database (tenant data, run state, artifacts).

​
Encryption

  • In transit: TLS 1.2 minimum, with HSTS enabled.
  • At rest: AES-256 via AWS KMS for all managed storage.

​
Authentication & authorization

  • Protocol: OAuth 2.1 with PKCE.
  • PKCE method: S256 only — plain is not accepted.
  • Discovery: Standard OAuth 2.1 discovery via RFC 9728 (Protected Resource Metadata) and RFC 8414 (Authorization Server Metadata).
  • Tokens: Bearer tokens; 15-minute access-token lifetime; refresh-token rotation with reuse-detection (a stolen refresh token invalidates the legitimate session).
  • Verification: Every MCP tool call re-verifies the bearer token with our authorization server before any handler runs.

​
Data handling

  • Tenant isolation: Every MCP tool call is scoped to the caller’s tenant ID. Cross-tenant reads are not possible from the MCP surface.
  • Bearer-token caching: Verified tokens are cached in-memory for the length of their lifetime. Raw tokens are not logged or persisted.
  • Tracing: LangSmith traces include user_email, tenant_id, session_id, and user-agent. Trace retention follows LangSmith’s defaults.
  • Artifact retention: Tool outputs (artifacts) are tenant-scoped and TTL’d: assets 30 days, agent outputs 7 days, intermediate results 24 hours.

​
Compliance

  • SOC 2: Type II attested (2026). Latest report available under NDA on request — contact legal@inflection.io.
  • Penetration testing: Independent third-party penetration test conducted in 2026; summary available under NDA on request.
  • GDPR: Data Processing Addendum available on request from legal@inflection.io.
  • CCPA: Compliant; California resident data subject rights honored per our Privacy Policy.
  • PCI / HIPAA: Not in scope. We do not process payment card data or protected health information.

​
Subprocessors

We share processing data with the following subprocessors:

​
CORS configuration

The MCP endpoint at mcp.inflection.io uses a wildcard CORS origin (Access-Control-Allow-Origin: *). This is deliberate. The security boundary on a remote MCP server is the OAuth 2.1 bearer token, not the origin. Access-Control-Allow-Credentials is set to false, which means browsers will not auto-attach cookies or HTTP-authentication credentials under wildcard CORS — CSRF against the MCP endpoint is structurally unreachable. The same wildcard pattern is used by every A-tier remote MCP (Notion, Linear, Atlassian, Stripe, GitHub, Asana). Restricting the CORS origin would block legitimate AI hosts that we have no advance knowledge of — the product depends on arbitrary client origins reaching the endpoint and presenting valid bearer tokens.

​
Support

  • General product support: support@inflection.io
  • Documentation: https://docs.inflection.io

​
Security disclosure

To report a security vulnerability, contact security@inflection.io

​
Change log