Help validate MCPAudit beta readiness with a redacted field report

[saagpatel]

MCPAudit is looking for two redacted config-only field reports before moving toward beta.

If you use MCP servers with Claude Desktop, Claude Code, Cursor, VSCode, Windsurf, or another MCP client, this should take a few minutes:

python3 -m pip install --upgrade mcp-audits
mcp-audit --version
mcp-audit scan --skip-connect --json mcp-audit-field-report.json --redact

Then open a redacted field-report issue:
https://github.com/saagpatel/MCPAudit/issues/new?template=field_report.md

The scan is config-only: it should not spawn MCP servers or contact remote endpoints.

Please redact credentials, private paths, internal hostnames, private URLs, customer names, workspace names, and proprietary prompt/resource/tool/schema text.

Details:
https://github.com/saagpatel/MCPAudit/blob/main/docs/EXTERNAL-FIELD-REPORT-REQUEST.md

Safe example shape:
https://github.com/saagpatel/MCPAudit/blob/main/docs/FIELD-REPORTS.md#minimal-public-example

Proof packet:
https://github.com/saagpatel/MCPAudit/blob/main/docs/MCP-TRUST-PACKET.md

Tracker:

• First external report: Collect first external redacted field report #83
• Second external report: Collect second external redacted field report #84

Solo evidence and generated demos help, but they do not replace external reports. The beta gate stays two accepted redacted reports from setups outside the maintainer checkout.