Routed endpoints

Most MCP servers run locally on the developer's machine, and the Endpoint Suite wraps them automatically. Routed endpoints covers the other case: a remote MCP server your team points tools at over the network.

Register one under MCP Inventory → Routed endpoints with an alias and its upstream HTTPS URL. Point your tools at the Sentilai URL instead of the vendor's. The Gateway then proxies that traffic and applies your MCP policy on the way through, exactly as it does for local servers.

Without this, a remote MCP server is a direct connection from the developer's machine to a third party, and neither your policy nor your audit trail sees it.

Routed endpoints: a remote MCP server reached through the Gateway, so policy and audit apply to it.