The MCP docs now say it plainly. The protocol can not vouch for a local server.
By Lior AharonovFounder, 7IT Solutions ·
What happened
On Monday, 5 October 2026, the MCP project merged a security guide for servers that run on your own machine. It names five threats (malicious servers, overcollecting servers, compromised dependencies, poisoned tool catalogs and vulnerable components) and calls running third-party servers in containers the most effective control.
Why it matters
A local server runs with your rights. Without isolation, the package you added for a weather lookup can read the same SSH keys you can.
What to do
Pin every local server to an exact version, give each one its own narrow token, and run third-party ones in a container that mounts only the project folder.

My take
Lior Aharonov
Founder, 7IT Solutions
Every npx line in your config is a stranger you let in with your keys. Treat it like one.
Sources
| MCP pull request 3072: local server security guide | github.com |
| MCP docs: Local server security | github.com |
Researched with AI tools; every fact is checked against the linked sources.