MCP Server Hosting: Remote MCP Servers on Dedicated Infrastructure

Why MCP Servers Need Dedicated Hosting

The Model Context Protocol gives AI agents structured access to external tools and data sources. But running an MCP server in production is fundamentally different from running one locally during development. Local servers die when your machine sleeps. They cannot serve multiple clients. They have no authentication, no audit trail, no crash recovery. When your AI agent depends on an MCP server for database access, file operations, or API integrations, downtime means your agent is blind and unable to act.

The June 2025 MCP specification update introduced streamable HTTP as the production transport, replacing the deprecated SSE approach. Streamable HTTP brings proper request-response semantics, chunked transfer encoding for long-running operations, and compatibility with standard HTTP infrastructure like load balancers, CDNs, and API gateways. But deploying streamable HTTP endpoints correctly requires session management, connection pooling, security headers, and CORS configuration that most teams get wrong on the first attempt.

osModa eliminates this complexity. The mcpd daemon handles streamable HTTP endpoint configuration, OAuth 2.1 token validation, connection lifecycle management, and watchdog supervision out of the box. You bring your MCP server code. osModa handles everything between your server and the outside world.

For a deep comparison of remote and local MCP deployment models, see our Remote vs Local MCP Servers guide. For transport-specific deployment guidance, see SSE / HTTP Deployment.

The mcpd Daemon: MCP Server Lifecycle Management

At the core of osModa's MCP hosting is mcpd -- a Rust-based daemon that manages the entire lifecycle of your MCP servers. It is part of osModa's suite of 9 Rust daemons and is purpose-built for the Model Context Protocol.

mcpd is open source. Inspect the implementation at github.com/bolivian-peru/os-moda. For hardening guidance, see the MCP Security Hardening guide.

Streamable HTTP: The Production MCP Transport

The MCP specification introduced streamable HTTP on March 26, 2025, and deprecated SSE in the June 18, 2025 spec update. Streamable HTTP replaces persistent SSE connections with a more scalable, bidirectional model that uses standard HTTP POST requests with chunked transfer encoding.

This transition matters for production hosting. SSE connections are persistent and stateful, making them difficult to load-balance and impossible to route through standard API gateways. Streamable HTTP uses the "sealed letter" model of standard HTTP requests, enabling traffic inspection, strict CORS enforcement, and session binding to verified user identities. It also works behind enterprise proxies and firewalls that terminate long-lived connections.

osModa's mcpd daemon implements streamable HTTP natively. When you deploy an MCP server, mcpd automatically configures the endpoint with proper chunked encoding, session management, and connection lifecycle handling. It also maintains backward compatibility with SSE for clients that have not yet migrated. Read the full deployment walkthrough in our SSE / HTTP Deployment guide.

[server.my-database-tools]
command = "node"
args = ["./mcp-db-server/index.js"]
transport = "streamable-http"
port = 8080
health_check = "/health"
restart_policy = "always"
max_restart_delay = "10s"

[server.my-database-tools.auth]
provider = "oauth2"
issuer = "https://auth.example.com"
audience = "mcp://my-database-tools"
scopes = ["tools:read", "tools:write"]

[server.my-database-tools.audit]
enabled = true
log_tool_calls = true
log_connections = true

Security: Zero Trust for MCP Servers

A 2025 research report analyzing 5,000 MCP servers found that 53% use insecure hard-coded credentials. By early 2026, over 8,000 MCP servers were found exposed without proper authentication. The MCP ecosystem is growing faster than teams can secure it.

osModa enforces zero trust by default. Every MCP server hosted on osModa gets OAuth 2.1 authentication with mandatory PKCE, scoped authorization for individual tools, trust boundary enforcement between servers, and tamper-proof audit logging of every tool call. The mcpd daemon validates every request before it reaches your MCP server code.

Each osModa server runs on dedicated Hetzner infrastructure with no multi-tenancy. MCP servers are isolated at the OS level with NixOS declarative security policies. Inter-server communication uses Noise_XX + ML-KEM-768 hybrid post-quantum encryption. For the full security implementation guide, see MCP Security Hardening.

Who Hosts MCP Servers on osModa

osModa serves teams that need MCP servers running reliably in production, not just on a developer's laptop during demos.

MCP Server Hosting Pricing

Every plan includes the full MCP hosting stack: mcpd daemon, streamable HTTP endpoints, OAuth 2.1 authorization, audit logging, watchdog auto-restart, NixOS atomic rollbacks, and dedicated Hetzner infrastructure. No per-request charges.

Frequently Asked Questions

Explore the MCP Hosting Ecosystem