Access types
Preview — part of the MCP Gateway private beta. Join the waitlist →
MCP servers are distributed in different ways, and the Gateway connects to each with the right controls. The MCP Rating registry classifies every server by access method, so you know what you're getting before you connect.
Local servers (sandboxed)
Spawned as a subprocess on your machine, then isolated:
| Access method | Runs as | Controls |
|---|---|---|
npm (npx) |
Node package | L1 / L2 sandbox + egress allowlist |
PyPI (uvx) |
Python package | L1 / L2 sandbox + egress allowlist |
Docker (docker run) |
Container image | Container isolation + egress allowlist |
Because the code runs locally, the Gateway can fully sandbox it.
Remote / web servers
Connected over the network via an MCP URL:
| Access method | Runs as | Controls |
|---|---|---|
| Remote (SSE / streamable HTTP) | Hosted by the provider | Connection policy + full audit logging |
Container-sandboxing doesn't apply — the server runs on the provider's infrastructure, not yours — but every call still passes through the Gateway's policy checks and the audit trail.
Why it matters
A web/remote server and a local npm package carry very different risks. The registry's access-method labels, plus the Gateway's per-type controls, let you choose and run each appropriately.