# MCP transport and network risks

URL: https://mcpservercybersecurity.com/mcp-risk-register/transport-and-network/
Updated: 2026-11-16

Seven transport and network risks cover DNS rebinding, listeners on all interfaces, server-side request forgery, cross-origin redirects, missing TLS, unbounded requests and open egress. Each row gives a control and a primary source from the MCP spec, release notes or an advisory, with severity set by the written rule, read on 16 Nov 2026.

## What this dimension covers

The channel between client and server: local listeners, TLS, redirects, request fetching and egress. The register holds 7 rows here (R-16, R-17, R-18, R-19, R-20, R-21, R-22). Each row states what the risk is, its impact, concrete controls and at least one primary source.

Sources: [MCP Streamable HTTP transport, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/streamable-http); [MCP Inspector 2.12.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.12.0); [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices).

## Highest-severity rows

Rows that meet the high rule under the written rule are: R-16 DNS rebinding against a local HTTP server; R-18 Server-side request forgery through discovery and fetch tools.

- R-16: The page can reach tools, tokens or files exposed by the local service. The Inspector's 2.12.0 release says a Host header check closes such a route to its API token and stored OAuth tokens.
- R-18: Internal services and cloud credentials become reachable from the machine running the client or server. Inspector 2.15.0 extended its fetch guard to metadata addresses beyond 169.254.0.0/16.

Sources: [MCP Streamable HTTP transport, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/streamable-http); [MCP Inspector 2.12.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.12.0); [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices); [MCP Inspector 2.15.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.15.0).

## First controls to apply

Start with the controls on the high rows, then work down. Controls name settings only where a primary source documents them; check each against the version your clients run.

- R-16: Validate the Origin header on every Streamable HTTP request and answer an invalid one with 403, as the spec requires.
- R-17: Bind to 127.0.0.1 unless network access is intended, as the spec advises.
- R-18: Require HTTPS for OAuth URLs and block private, loopback and link-local ranges with a maintained library, not hand-written parsing.
- R-19: Follow redirects only within the same scheme, host and port, as Python SDK 2.2.0 does by default.
- R-20: Use TLS for every remote Streamable HTTP connection.
- R-21: Set request size, session count and idle-timeout limits (Python SDK 2.2.0 expires idle legacy sessions after 30 minutes and caps them at 10,000).
- R-22: Disable network access for servers that do not need it and allow-list destinations for those that do.

Sources: [MCP Streamable HTTP transport, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/streamable-http); [MCP Inspector 2.12.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.12.0); [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices); [MCP Inspector 2.15.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.15.0).

## Transport and network: 7 items

### R-16: DNS rebinding against a local HTTP server

A web page the user visits uses a domain that later resolves to the user's own machine to talk to a local MCP server or developer tool that listens on HTTP.

**Impact:** The page can reach tools, tokens or files exposed by the local service. The Inspector's 2.12.0 release says a Host header check closes such a route to its API token and stored OAuth tokens.

**Controls:**

- Validate the Origin header on every Streamable HTTP request and answer an invalid one with 403, as the spec requires.
- Validate the Host header against an allow-list.
- Require an authorization token for local HTTP servers, or use stdio.

Severity: high

Sources: [MCP Streamable HTTP transport, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/streamable-http) (read 2026-11-16); [MCP Inspector 2.12.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.12.0) (read 2026-11-16).

### R-17: Local server listening on all interfaces

A server meant for the local machine binds to 0.0.0.0, so other hosts on the network can connect.

**Impact:** Anyone on the network can reach tools that were meant for one user.

**Controls:**

- Bind to 127.0.0.1 unless network access is intended, as the spec advises.
- Use stdio, or a Unix domain socket with restricted permissions, for local servers.
- Scan developer subnets for unexpected MCP listeners.

Severity: medium

Sources: [MCP Streamable HTTP transport, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/streamable-http) (read 2026-11-16); [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices) (read 2026-11-16).

### R-18: Server-side request forgery through discovery and fetch tools

A client follows URLs supplied by a server (OAuth metadata, redirects), or a tool fetches URLs produced by a model, and the target is an internal address or a cloud metadata service.

**Impact:** Internal services and cloud credentials become reachable from the machine running the client or server. Inspector 2.15.0 extended its fetch guard to metadata addresses beyond 169.254.0.0/16.

**Controls:**

- Require HTTPS for OAuth URLs and block private, loopback and link-local ranges with a maintained library, not hand-written parsing.
- Validate redirect targets and pin DNS results between check and use.
- Send server-side fetches through an egress proxy that enforces destination policy.

Severity: high

Sources: [MCP Security Best Practices, 2026-07-28 revision](https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices) (read 2026-11-16); [MCP Inspector 2.15.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.15.0) (read 2026-11-16).

### R-19: Credentials carried across cross-origin redirects

An HTTP client follows a redirect to another origin and sends Authorization headers or cookies with it. Advisories for the Python SDK (GHSA-5h93-6whr-6q8j) and the TypeScript client SDK (GHSA-6prh-2h8m-c8cw) describe the pattern.

**Impact:** A server or an intermediary can collect credentials meant for another host.

**Controls:**

- Follow redirects only within the same scheme, host and port, as Python SDK 2.2.0 does by default.
- Drop Authorization and cookie headers on any cross-origin redirect.
- Upgrade to the SDK versions named in the advisories.

Severity: medium

Sources: [GHSA-5h93-6whr-6q8j: MCP Python SDK cross-origin redirects](https://github.com/advisories/GHSA-5h93-6whr-6q8j) (read 2026-11-16); [GHSA-6prh-2h8m-c8cw: MCP TypeScript client SDK cross-origin redirects](https://github.com/advisories/GHSA-6prh-2h8m-c8cw) (read 2026-11-16); [MCP Python SDK v2.2.0 release notes](https://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0) (read 2026-11-16).

### R-20: Remote server without TLS or with unverified identity

A client connects to a remote MCP server over plain HTTP, or without checking who the server is.

**Impact:** Traffic and tokens can be read or changed in transit, and a different server can answer.

**Controls:**

- Use TLS for every remote Streamable HTTP connection.
- Keep client runtimes current: Inspector 2.13.0 notes that certificate checks rely on the Node.js runtime and names patched Node.js releases after an October 2026 CA issue.
- Reject http URLs for OAuth endpoints except loopback addresses during development.

Severity: medium

Sources: [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html) (read 2026-11-16); [MCP Inspector 2.13.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.13.0) (read 2026-11-16).

### R-21: Unbounded requests and sessions exhaust a server

An HTTP server accepts requests or sessions without limits. GHSA-46jr-4wx8-v453 (TypeScript SDK) and GHSA-84m7-p3x7-pcfv (Python SDK) describe memory and session exhaustion.

**Impact:** A single unauthenticated client can stop the service. Impact is availability only.

**Controls:**

- Set request size, session count and idle-timeout limits (Python SDK 2.2.0 expires idle legacy sessions after 30 minutes and caps them at 10,000).
- Apply rate limits and quotas per tenant.
- Authenticate requests before they reach the SDK.

Severity: low

Sources: [GHSA-46jr-4wx8-v453: MCP TypeScript SDK memory exhaustion](https://github.com/advisories/GHSA-46jr-4wx8-v453) (read 2026-11-16); [GHSA-84m7-p3x7-pcfv: MCP Python SDK session accumulation](https://github.com/advisories/GHSA-84m7-p3x7-pcfv) (read 2026-11-16); [MCP Python SDK v2.2.0 release notes](https://github.com/modelcontextprotocol/python-sdk/releases/tag/v2.2.0) (read 2026-11-16).

### R-22: Unrestricted outbound access from server processes

A server process can open connections to any host, so a flaw or a malicious package can send data anywhere.

**Impact:** Stolen data leaves the machine without a block. The altered SP-API package described by Knostic sent credentials to a hardcoded IP.

**Controls:**

- Disable network access for servers that do not need it and allow-list destinations for those that do.
- Log and alert on connections from MCP server processes to new destinations.
- Use an egress proxy for server-side deployments.

Severity: medium

Sources: [Local Server Security, modelcontextprotocol.io](https://modelcontextprotocol.io/docs/tutorials/security/local-server-security) (read 2026-11-16); [Repackaged Amazon SP-API MCP Sends App Secrets to an Undisclosed IP, Knostic](https://www.knostic.ai/blog/repackaged-amazon-sp-api-mcp-sends-app-secrets-to-an-undisclosed-ip) (read 2026-11-16).

## Related pages

- [The full MCP Risk Register](/mcp-risk-register/)
- [Authorization](/mcp-risk-register/authorization/)
- [Tool descriptions and schemas](/mcp-risk-register/tool-descriptions-and-schemas/)
- [Method](/mcp-risk-register/methodology/)
- [MCP Security Checklist](/mcp-security-checklist/)
