Jest Snapshot Pii Audit
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Oct 24, 2026
15 rules that find the real customer data your .snap files committed
The publisher's own server: audit.domains - Domain Valuation
Overview
Local stdio MCP server that audits Jest snapshot files for committed customer data using 15 detection rules.
- What you can do
- Scan Jest .snap snapshot files for embedded real customer data.
- Apply 15 rules to flag likely personal or sensitive values committed in snapshots.
- Report findings so an assistant can help review and clean up test fixtures.
- No individual tools are listed in the manifest, so exact operations are not documented.
- When to use it
- Useful when a JavaScript or TypeScript project keeps Jest snapshots in version control and you want to check whether real customer data leaked into them before sharing, releasing or cleaning up test fixtures.
- Requirements
- Runs as a local process over stdio, started with npx from the npm package @readystack/jest-snapshot-pii-audit. Requires Node.js and network access to fetch the package; no authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Jest Snapshot Pii Audit 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.2LatestSep 19, 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.
Other Audit integrations
audit.domains - Domain Valuation
domains.auditOfficial publisher
Deterministic domain-name valuation: fair-value intervals, comparable recorded sales, availability checks, and a verified for-sale listing market.
Revenue Agent — OpenAPI Audit & Change Detection
news.prhOfficial publisher
A remote MCP endpoint that audits OpenAPI specifications and detects API changes, charging $0.10 USDC per analysis via x402 on Base.
SEO Audit & Broken Link Checker
Published by GitHub account prometheus-maker
An Apify-hosted MCP server that audits a website's pages for SEO metadata and finds broken links and images, returning per-page scores.
FinePrint AI Legal Risk & Contract Audit MCP Server
Published by GitHub account RitualDev-Lab
Local in-memory scanner that grades legal contracts, NDAs and leases for risk and drafts redline amendments for coding agents.
Mcp Supply Audit
Published by GitHub account kimmawla
Audits MCP servers as supply-chain artifacts — registry entries, PyPI/npm packages, client configs and tool definitions — using read-only static checks.