MCP infrastructure
MCP Server Hosting: Best Platforms for Secure Remote MCP
Remote MCP servers are now much closer to ordinary HTTP services than earlier stateful deployments. That makes VPS, container, serverless, and managed application infrastructure viable choices, but authentication, authorization, tool exposure, logging, and network boundaries remain critical.
Remote MCP Server Architecture
The current MCP specification (2026-07-28) uses a stateless protocol core for remote operation. Requests can be routed across normal HTTP infrastructure without requiring sticky sessions, while method and tool information can be surfaced through request headers for gateways and policy layers.
MCP Server Hosting Options Compared
| Deployment | Good fit | Main tradeoff | Choose when |
|---|---|---|---|
| VPS / VM | Maximum infrastructure control, persistent services, custom networking | You operate the host — patches, backups, monitoring, uptime | You need full control over the runtime environment or have existing server infrastructure |
| Containers (Docker, K8s) | Repeatable deployments, horizontal scaling, isolation between MCP servers | Host and container boundaries still need hardening; orchestration adds complexity | You run multiple MCP servers or need reproducible deployments across environments |
| Serverless / edge | Stateless request-driven MCP workloads, pay-per-invocation | Runtime limits (timeout, memory, cold start) vary by platform | MCP tools are lightweight, stateless, and bursty — good for read-only data tools |
| Managed application platform | Lower operational burden, built-in TLS and scaling | Less low-level control over networking, runtime, and dependencies | You want to deploy MCP servers without managing infrastructure directly |
Remote MCP Server Security Requirements
Because MCP servers expose tool capabilities over HTTP, security requirements mirror those of any API that performs actions on behalf of a caller — plus the additional concern that the caller is an autonomous agent that may invoke tools in unexpected sequences.
- Authenticate clients before granting access to protected tools.
- Authorize operations using the narrowest useful scopes.
- Separate public transport access from sensitive backend credentials.
- Rate-limit high-impact or expensive tools independently.
- Record tool calls and failures for audit and incident review.
- Do not expose administrative or destructive tools without explicit policy.
- Validate tool inputs — agents can produce unexpected argument combinations.
MCP Server Deployment Checklist
- Is the MCP server accessible only over HTTPS with valid certificates?
- Does the server authenticate clients before accepting tool calls?
- Are tool permissions scoped to what each client actually needs?
- Are backend credentials (database, APIs) isolated from the MCP transport layer?
- Is there rate limiting on expensive or destructive tools?
- Are tool calls logged with enough context for audit and debugging?
- Is trace-context propagation enabled for distributed tracing?
- Is the deployment reproducible (infrastructure as code, container image, CI/CD)?
MCP Server Observability and Distributed Tracing
The current MCP specification supports W3C Trace Context propagation so an MCP tool call can participate in a broader distributed trace across the agent, gateway, MCP server, and downstream services. This means your MCP server's tool calls can appear in the same trace as the agent's model calls and other API interactions, making end-to-end debugging practical.
Sources
- MCP 2026-07-28 specification release— Current MCP authorization, transport and protocol changes
- MCP 2026-07-28 release candidate — tracing— W3C Trace Context propagation across hosts, SDKs, servers and downstream services
- MCP TypeScript SDK v2— Stable SDK line implementing the 2026-07-28 specification
Agent Infrastructure Recommendation Kit
Turn your MCP hosting plan into a documented architecture decision
The Recommendation Kit covers platform selection, security controls, observability, and deployment checklists for MCP server infrastructure so you can defend your hosting choice.
Get the Recommendation Kit — $19