Open source · Apache-2.0 · early access

Ship MCP servers you can actually trust.

MCPShield is a Rust runtime sandbox for Model Context Protocol servers. A drop-in wrapper that enforces capability allowlists, filters outbound traffic and seals every policy it enforces — aligned to the NSA May-2026 MCP guidance, in a single cargo add.

  • Apache-2.0 open source
  • NSA May-2026 MCP guidance aligned
  • OTel GenAI semconv v1.36+
  • 100% Rust — zero GC pauses
  • EU data residency by default
The gap

The MCP spec stops at the protocol. Attackers don't.

An MCP server hands a model real tools — a filesystem, a database, an outbound network. The spec says nothing about who's allowed to call what, what may leave the box, or how to prove what you enforced. That's the boundary MCPShield owns.

  • Prompt-injected tool calls

    A poisoned document tells the model to read your secrets and POST them out.

  • Over-broad capabilities

    A server scoped to one folder quietly reaches the whole filesystem.

  • Silent data exfiltration

    Sensitive payloads leave over an unmonitored outbound connection.

  • No evidence trail

    When audit asks what was enforced, you have logs — not proof.

How it works

Four gates between the model and the world

Every call runs the same ordered pipeline at the runtime boundary — not bolted on after. Default deny, end to end.

  1. 01

    Capability allowlist

    Only the tools and resource URIs you approve ever reach the wrapped server. Everything else is denied by default.

  2. 02

    Proxy filter + DLP

    Every outbound call clears the host filter, regex DLP and IOC corpus before it is allowed to leave the sandbox.

  3. 03

    Behavioral telemetry

    Tool-call events export as OpenTelemetry GenAI semconv v1.36+ spans — no custom agent, no sidecar.

  4. 04

    Sealed attestation

    Policies are cryptographically signed, so you can prove exactly which guardrails were enforced for every deployment.

Pricing

Start free. Pay when you need the network.

The runtime is open source and yours to self-host. The cloud adds the cross-tenant threat-intel network and attestation you can't build alone.

Free

€0/forever

Protect your MCP servers with your own rules and see your own data.

  • Open-source runtime — full enforcement, self-hosted
  • Capability allowlist, outbound proxy + DLP
  • Your own detection events in the console
  • 7-day retention
  • Community support
Most popular

Team

€349/per month

Stop defending alone — get the cross-tenant threat intelligence network.

  • Everything in Free
  • Cross-tenant threat-intel network — protected against attacks seen elsewhere
  • Fleet management + cohort policy templates
  • 30-day retention
  • Email support

Enterprise

Custom/contact us

Attestation, compliance evidence and identity for security-led procurement.

  • Everything in Team
  • Cryptographic supply-chain attestation (DIF MCP-I)
  • SOC 2 evidence packs + DPA
  • SSO / SCIM provisioning
  • EU data residency (GDPR)
  • 365-day retention, dedicated support + SLA

Compare every tier on the full pricing page.

OSS quickstart

Wrap a server in minutes

Add the crates to your workspace, declare a capability allowlist and outbound filter, and wrap any stdio MCP server. No daemon, no sidecar — the sandbox runs in-process.

Cargo.toml
# Cargo.toml
[dependencies]
mcpshield-runtime = { git = "https://github.com/mcpshieldvow/mcpshield-runtime" }
mcpshield-policy  = { git = "https://github.com/mcpshieldvow/mcpshield-runtime" }
mcpshield-telemetry = { git = "https://github.com/mcpshieldvow/mcpshield-runtime" }

Start securing your MCP deployment

Join the early-access program for the hosted control plane, or pull the crates and self-host today. Both speak the same telemetry.