Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for infrastructure teams experimenting with MCP in sensitive environments and wanting a concrete sandboxing approach beyond prompt-level tool restrictions.
Who should use it
Who should skip it
Hold off on facebook/mcpguard-dynamic if the setup requirements exceed what your current workflow or team can support without dedicated engineering time.
About this signal
facebook/mcpguard-dynamic is tracked by RepoRadar as a security sandbox in the AI Infrastructure section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'worth watch' with a Silver tier and hard setup difficulty. facebook/mcpguard-dynamic leads on novelty (9.0) and open-source/build quality (8.4); its lowest signal is setup ease (4.2), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned facebook/mcpguard-dynamic a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The strongest protection paths require Linux kernel 6.x with BPF LSM plus root-level setup, so evaluate it on a disposable host before touching shared infrastructure; It is a sandboxing layer for MCP servers rather than a turnkey desktop feature, so teams still need their own policy review and operational logging around what tool access is allowed.