Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers shipping MCP servers into real environments where 'it works on my machine' is not enough and you need a fast way to sanity-check prompt surfaces, transports, and tool schemas before other agents touch them.
Who should use it
Who should skip it
Skip DaoyuanLi2816/mcp-fence if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
DaoyuanLi2816/mcp-fence is tracked by RepoRadar as a security tool in the MCP / Tooling section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, DaoyuanLi2816/mcp-fence is strongest on workflow potential (9.4) and open-source/build quality (8.4) and weakest on maturity (5.8) — a profile worth weighing against your own priorities. 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 DaoyuanLi2816/mcp-fence a composite score of 7.9 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
Dynamic scans and fuzzing can hit live tools or backing services, so first runs should stay on test targets and avoid the unsafe modes until the safe report looks clean; The sandbox workflow still executes the server entrypoint inside Docker, so teams should review startup commands before treating the container profile as a full trust substitute.