io.github.firebase/firebase-mcp
NPM · FIREBASE-TOOLS · SCANNED SEP 20
Gives AI development tools Firebase-specific capabilities and expertise.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security77
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects tar 6.2.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 711 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the io.github.firebase/firebase-mcp server?
io.github.firebase/firebase-mcp runs locally as an npm package, launched with npx -y firebase-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · firebase-tools
claude mcp add firebase-firebase-mcp -- npx -y firebase-tools
{
"mcpServers": {
"firebase-firebase-mcp": {
"command": "npx",
"args": [
"-y",
"firebase-tools"
]
}
}
} {
"servers": {
"firebase-firebase-mcp": {
"command": "npx",
"args": [
"-y",
"firebase-tools"
]
}
}
} codex mcp add firebase-firebase-mcp -- npx -y firebase-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"firebase-firebase-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"firebase-tools"
],
"enabled": true
}
}
} openclaw mcp add firebase-firebase-mcp --command npx --arg -y --arg firebase-tools
mcp_servers:
firebase-firebase-mcp:
command: "npx"
args: ["-y", "firebase-tools"] {
"McpServers": {
"firebase-firebase-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"firebase-tools"
]
}
}
} assistant mcp add firebase-firebase-mcp -t stdio -c npx -a -y firebase-tools
{
"mcpServers": {
"firebase-firebase-mcp": {
"command": "npx",
"args": [
"-y",
"firebase-tools"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Sept 26 0
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Security disclosure: fail → unverified ▼ functional
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Sept 26 0
- CVE-2026-85063 affects this package: high ▼ security
- 4 Sept 26 0
- CVE-2026-71429 affects this package: high ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/firebase-tools@14.27.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 16 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-8988-4f7v-96qf | CVE-2026-54285 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-8cw4-87c7-c6xx | CVE-2026-85063 | medium | yes | |
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-23hp-3jrh-7fpw | CVE-2026-59873 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-34x7-hfp2-rc4v | CVE-2026-24842 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N | yes |
| GHSA-83g3-92jg-28cx | CVE-2026-26960 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N | yes |
| GHSA-8qq5-rm4j-mr97 | CVE-2026-23745 | high | yes | |
| GHSA-8x88-c5mf-7j5w | CVE-2026-59874 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-9ppj-qmqm-q256 | CVE-2026-31802 | high | yes | |
| GHSA-gvwx-54wh-qm9j | CVE-2026-59875 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-qffp-2rhf-9h96 | CVE-2026-29786 | high | yes | |
| GHSA-r292-9mhp-454m | CVE-2026-73566 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-r6q2-hw4h-h46w | CVE-2026-23950 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L | yes |
| GHSA-vmf3-w455-68vh | CVE-2026-53655 | medium | yes | |
| GHSA-w8wr-v893-vjvp | CVE-2026-59871 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 5 |
| Stale | 130 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the io.github.firebase/firebase-mcp server?
io.github.firebase/firebase-mcp is listed in the public MCP registry as io.github.firebase/firebase-mcp. Gives AI development tools Firebase-specific capabilities and expertise. This page covers its npm package (firebase-tools).
Is the io.github.firebase/firebase-mcp server safe to use?
io.github.firebase/firebase-mcp scores 32 out of 100 on VerifyMCP. We recorded 16 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the io.github.firebase/firebase-mcp server still maintained?
io.github.firebase/firebase-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.firebase/firebase-mcp server under?
io.github.firebase/firebase-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.