# Remote MCP Server Hosting UK

Source: https://dijihost.co.uk/mcp-server-hosting/
Updated: 2026-11-12

> dijitul hosts remote MCP (Model Context Protocol) servers for UK businesses, quoted to your setup. We run your MCP server on a managed VPS behind HTTPS, with the Streamable HTTP transport, OAuth-based authorisation or API keys, Origin header checks, request logging without secrets, and monitoring, so AI assistants can call your tools and data safely.

## Key facts

- Quoted per server after a short technical review
- Built for the Streamable HTTP transport in the current MCP specification (2026-07-28)
- HTTPS only, through Nginx and Cloudflare
- OAuth 2.1 authorisation as described in the MCP spec, or API keys for internal tools
- Origin header validation and rate limiting
- Structured logs of tool calls, with tokens and secrets stripped
- Node.js, Python and Docker-based MCP servers

## What a remote MCP server is

The Model Context Protocol lets AI assistants such as Claude, ChatGPT and coding agents call tools and read data from systems you control. A **local** MCP server runs on one person's computer over stdio. A **remote** MCP server runs on a server and is reached over the internet, so a whole team, or your customers, can connect to the same tools.

The current specification, revision 2026-07-28, defines two standard transports: stdio and **Streamable HTTP**. With Streamable HTTP the server exposes a single endpoint, such as https://mcp.example.co.uk/mcp, and every message is an HTTP POST. Replies come back as JSON or as a Server-Sent Events (SSE) stream for that request. The older HTTP+SSE transport from 2024 is deprecated.

## What we set up

- **HTTPS** with automatic certificate renewal and Cloudflare in front.
- **A reverse proxy** tuned for streaming. The spec says servers should send X-Accel-Buffering: no on SSE responses so proxies such as Nginx do not hold messages back, and we match the timeouts to your longest tool call.
- **Process management** with systemd, PM2 or Docker, restarting the server if it crashes.
- **Separate staging and production** endpoints if you are still changing tools.
- **Uptime and error monitoring**, alerting us when the endpoint stops answering.

## Authentication and security

An MCP server can read your data and take actions, so access control matters more than usual. The MCP specification says authorisation is optional, but where it is used over HTTP it is based on OAuth 2.1. Points from the spec worth knowing:

- MCP servers that use authorisation must publish OAuth 2.0 Protected Resource Metadata (RFC 9728) so clients can find the authorisation server.
- Clients send tokens in the Authorization: Bearer header on every request, never in the URL query string.
- Servers must check that a token was issued for them, and must not pass other tokens through to upstream APIs.
- Servers must validate the Origin header to block DNS rebinding attacks, and return 403 for an invalid Origin.

For an internal tool used only by your staff, a simpler API key or an identity-aware proxy can be enough. We help you choose and set it up. If the server wraps your own APIs, see [API hosting](https://dijihost.co.uk/api-hosting/).

## Logging without leaking

When an assistant calls a tool, you want to know who called what, when, and whether it worked. We log the method, tool name, status, duration and the authenticated user, and strip access tokens and API keys from the logs. The Streamable HTTP transport now mirrors the method and tool name into Mcp-Method and Mcp-Name headers, which makes it easier to log and rate-limit at the proxy without reading request bodies. Logs are rotated and kept for a period you choose.

## Older MCP clients

The 2026-07-28 revision removed protocol-level sessions and the separate GET stream. Clients built for revisions 2025-03-26 to 2025-11-25 may still send an Mcp-Session-Id header. If you need to support both, your server's SDK has to handle the fallback, and we make sure the proxy passes the right methods and headers through. Tell us which assistants will connect and we will test with them before go-live.

*Sources, checked 11 November 2026: [MCP transports](https://modelcontextprotocol.io/specification/latest/basic/transports); [MCP Streamable HTTP](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/streamable-http); [MCP authorization](https://modelcontextprotocol.io/specification/latest/basic/authorization).*

## FAQs

### Where can I host a remote MCP server in the UK?

dijitul hosts remote MCP servers on managed UK servers with HTTPS, the Streamable HTTP transport, authentication, Origin checks, logging and monitoring. It is quoted per server, and we can host Node.js, Python or Docker-based MCP servers.

### What is the difference between a local and a remote MCP server?

A local MCP server runs on one computer and talks to the AI client over stdio. A remote MCP server runs on a web server and is reached over HTTPS using Streamable HTTP, so many users and assistants can share the same tools.

### Does an MCP server need authentication?

The MCP specification makes authorisation optional, but any server that exposes real data or actions should have it. Over HTTP the spec bases authorisation on OAuth 2.1, with tokens sent in the Authorization header. Internal tools can sometimes use API keys instead.

### Is the HTTP+SSE transport still supported?

It is deprecated. The MCP specification has marked the 2024-11-05 HTTP+SSE transport as deprecated since revision 2025-03-26 and says new servers should use Streamable HTTP. Servers can keep the old endpoints for older clients if needed.

### Why does my MCP server work locally but not behind Nginx?

Usually because the proxy buffers the SSE stream or times out long tool calls. The MCP spec recommends sending X-Accel-Buffering: no on SSE responses. Proxy timeouts also need to be longer than your slowest tool. dijitul configures this for MCP servers it hosts.

## Pricing and ordering

This is quoted to fit. Request a quote at https://dijihost.co.uk/quote/ or call 01623 650333.
