Firebase Deploy Leak Audit

Reads firebase.json and lists the files a Firebase deploy would publish publicly, so an assistant can flag accidental leaks.

What you can do

This local MCP server inspects a project's firebase.json configuration and reports which files the next firebase deploy would publish to the open web. Its purpose is to surface files that would become publicly reachable before a deploy happens. The registry description states it reads firebase.json and names the files your next firebase deploy would publish to the open web. No individual tools are listed in the manifest.

When to use it

Use it when preparing or reviewing a Firebase Hosting deploy and you want a quick check of what would become publicly accessible. It is aimed at catching files that should not be exposed before they are published.

Requirements

Runs locally as a stdio process, started with npx from the npm package @readystack/firebase-deploy-leak-audit. Node.js and npx are therefore required. No authentication, environment variables, or headers are declared. It is desktop only and not available as a web executable.