
Firestore Rules Guard
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.4Updated Oct 24, 2026
Audits firestore.rules and storage.rules for public access, expired test-mode dates and missing owne
Overview
Local MCP server that audits Firestore and Storage security rules files for public access, expired test-mode dates and missing ownership checks.
- What you can do
- Audit firestore.rules and storage.rules files for rules that allow public access.
- Flag expired test-mode dates and missing ownership checks in those rule files.
- Report findings back to the assistant so it can explain or fix the rules.
- No individual tools are listed in the manifest, so the exact operations are not documented.
- When to use it
- Useful when a project keeps Firebase Firestore or Cloud Storage security rules in the repository and you want an assistant to review them before deploying or during a security pass.
- Requirements
- Runs as a local stdio process on the user's machine, started with npx from the npm package; Node.js and network access for the package download are implied. No authentication, environment variables or headers are declared. Desktop client only.
Installation
In SourceWeft
- Open Firestore Rules Guard in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
1- v1.0.4LatestSep 23, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.