Stytch
Connect Stytch to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Stytch connection as identity & sso evidence. Automated collection is not available for this provider yet.
| Category | Identity & SSO |
| Connect with | API token, MCP server |
| What a connection produces | Connection record |
Connect with an API token
-
In Stytch:
- Sign in to the Stytch Dashboard and select your project (use the Live environment).
- Open the Project ID & API keys section and copy the project's secret.
Where to find the other values:
- Account / Org / Workspace (optional): The Project ID & API keys section of the Stytch Dashboard shows the Project ID.
Stytch's public documentation does not cover every step.
The fetched page only names the Project ID & API keys section; the steps to create a new secret, whether a secret is shown only once, and any read-only option were not documented there. Stytch API calls use the Project ID and secret together. Re-verify in the dashboard.
Source: stytch.com, checked 2026-10-07.
-
On Compliance › Connectors, open Stytch, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Connect with the MCP server
Choose MCP server: the address https://mcp.stytch.dev/mcp is filled in. Sign in to Stytch when asked. It lets Griffin AI search Stytch.
Frameworks
No automated compliance test reads Stytch yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Identity & SSO connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks