Is MetaMCP MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
What to know before installing
- highShell command built from a string (injection risk)
How MetaMCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 71/100
- higher than 36% of 48,255 servers
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 2 read · 1 change
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
1 high
- Code scan69 source files scanned13/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 32 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (1)
- highShell command built from a string (injection risk)
exec.shell-concatdist/oauth-provider.js: …l.toString(); try { execSync(`open "${url}"`, { stdio: 'ignore' }); } …
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON