Is Firebase MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
No critical or high findings in the latest scan.
How Firebase compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 56% of 45,646 servers
- Tools that change things
- 27%
- typical: 0%. Fewer write tools means less an agent can break
What its tools let an agent do: 35 read · 6 create · 6 change · 2 delete · 1 send or post · 2 run or deploy
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
2 medium
- Code scan837 source files scanned15/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 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Findings (2)
- mediumGoogle API key in source (often public by design; check its restrictions)
secret.googlelib/api.js: …Override("FIREBASE_DYNAMIC_LINKS_KEY", "AIza****"); exports.dynamicLinksKey = dynamicLin… - mediumeval / new Function used
exec.evallib/deploy/functions/runtimes/node/triggerParser.js: …ocess.exit(0); }; const dynamicImport = new Function("modulePath", "return import(modulePath)…
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON