Local Server Security changeddocs/2026-07-28/tutorials/security/local-server-security
Nearest release: v2.1.290, published 2 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 5 Oct 2026 20:31 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+9added
Lines−9removed
From line
4
where the diff opens
First seen
5 Oct 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 4, old and new numbered
/
from line 4
44
55Most MCP security documentation covers the protocol threat model: OAuth flows,
66token handling, session hijacking, and confused deputy attacks. For those, see
7[Authorization](/docs/2026-07-28/tutorials/security/authorization) and
8[Security Best Practices](/docs/2026-07-28/tutorials/security/security_best_practices).
7[Authorization](/docs/2026-07-28/tutorials/security/authorization.md) and
8[Security Best Practices](/docs/2026-07-28/tutorials/security/security_best_practices.md).
99
1010This guide covers a different threat model: **your machine**. When you run an
1111MCP server locally, you download code from the internet and run it as a child
from line 46
4646
4747Clients that offer one-click installation are required to show you the exact
4848command before it runs
49([SEP-1024](/seps/1024-mcp-client-security-requirements-for-local-server-)),
49([SEP-1024](/seps/1024-mcp-client-security-requirements-for-local-server-.md)),
5050but a consent dialog only helps if you know what to look for. That is what
5151the rest of this guide is about.
5252
from line 131
131131your laptop, while you take on everything else in this guide for no benefit.
132132
133133* **Prefer the remote version where one exists.** A server offered over
134 [Streamable HTTP](/specification/2026-07-28/basic/transports/streamable-http)
134 [Streamable HTTP](/specification/2026-07-28/basic/transports/streamable-http.md)
135135 runs no code on your machine, uses the protocol's authorization flow
136136 instead of a token in a local config file, and is patched in one place.
137137 The protocol threat model (linked above) applies to it instead of this
from line 197
197197
198198* **Read the tool list before you rely on a server.** Most clients can show
199199 each tool's description, and the
200 [MCP Inspector](/docs/2026-07-28/tools/inspector) lists every tool a
200 [MCP Inspector](/docs/2026-07-28/tools/inspector.md) lists every tool a
201201 server exposes without a model in the loop. If a description contains
202202 instructions that have nothing to do with the tool's job, remove the
203203 server.
from line 419
419419
420420## Next Steps
421421
422> **[Security Best Practices](/docs/2026-07-28/tutorials/security/security_best_practices)**
422> **[Security Best Practices](/docs/2026-07-28/tutorials/security/security_best_practices.md)**
423423>
424424> The protocol threat model: confused deputy, token passthrough, and session
425425> hijacking
426426
427> **[Authorization](/docs/2026-07-28/tutorials/security/authorization)**
427> **[Authorization](/docs/2026-07-28/tutorials/security/authorization.md)**
428428>
429429> How OAuth-based authorization works for remote MCP servers
430430
431> **[SEP-1024](/seps/1024-mcp-client-security-requirements-for-local-server-)**
431> **[SEP-1024](/seps/1024-mcp-client-security-requirements-for-local-server-.md)**
432432>
433433> Client security requirements for local server installation consent
434434
435> **[Connect to local servers](/docs/2026-07-28/develop/connect-local-servers)**
435> **[Connect to local servers](/docs/2026-07-28/develop/connect-local-servers.md)**
436436>
437437> Set up local servers in your client — the workflow this guide secures
438438
No line in this hunk matches that.