What it does
The server reads a project's firebase.json configuration and names the files that the next firebase deploy would make publicly reachable. It is aimed at checking what a Firebase Hosting deployment would expose before it goes live, so that unintended files can be spotted in advance.
It is relevant to developers and teams working with Firebase deployments who want to review publish scope as part of security or deployment checks. The entry is classified under cloud-devops, development and security.
The publisher's description gives no further details on installation, setup or runtime requirements, so those are not described here.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.jmshinhwa/firebase-deploy-leak-audit
Reads firebase.json and names the files your next firebase deploy would publish to the open web
v1.0.5As shown on registry.modelcontextprotocol.io when we last read it