Security and network
What your network has to reach, how sign-in works, and the OAuth details a security review asks for.
The short version, for whoever approves the connection:
- Your users sign in with their own Simetrik account. There's no shared key or service account. Every request runs as the person who signed in, with their role — never more.
- Nothing is installed. Clients talk to one HTTPS address per region.
- Each region is separate. A region's server only reaches that region's Simetrik, and keeps its sessions in that region.
- The server keeps sessions, not your data. Results go back to your client and aren't stored by the server.
What your network has to allow
Your users' clients and browsers need outbound HTTPS (port 443) to:
| Host | What for |
|---|---|
mcp.<region>.simetrik.com | The server: every tool call, plus the sign-in endpoints below |
accounts.simetrik.com | Simetrik sign-in, shown in the browser while connecting |
| Your identity provider | Whatever you already use to sign into Simetrik (for example Google) |
That's the whole list on your side. The server itself reaches the Simetrik platform in the same region — and, only when someone uses the Simetrik Agent, Simetrik's agent service. Those calls are server to server, so there's nothing for you to open.
Need something this page doesn't cover for your review? Ask your Simetrik contact.