Collect second external redacted field report

[saagpatel]

Goal

Collect a second external, redacted, config-only MCPAudit field report from a meaningfully different setup or downstream consumer path.

Current release/context

MCPAudit v1.13.1 is live. The generator-to-auditor proof packet is now on main:
https://github.com/saagpatel/MCPAudit/blob/main/docs/MCP-TRUST-PACKET.md

The trust packet explains the public story: mcpforge can scaffold or generate a reproducible MCP server, MCPAudit audits the trust boundary, and bridge-db stays local dogfood/receipt infrastructure rather than a public product claim. This second report still needs to come from a meaningfully different setup or consumer path than #83.

Send this ask

Use the second-tester message here:
https://github.com/saagpatel/MCPAudit/blob/main/docs/EXTERNAL-OUTREACH-MESSAGES.md#direct-ask-for-second-tester

Request packet:
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

Public field-report template:
https://github.com/saagpatel/MCPAudit/issues/new?template=field_report.md

Safe collection path

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

Acceptance criteria

• Report comes from a different environment, MCP client mix, or consumer workflow than the first accepted field report.
• Report states MCPAudit version, OS, MCP client names, approximate server count, and whether a JSON/SARIF/dashboard/CI consumer parsed it.
• Snippet follows the safe example shape and is redacted: no credential values, private paths, internal hostnames, private URLs, customer names, workspace names, or proprietary prompt/resource/tool/schema text.
• Reporter confirms whether the redacted shape can become a public fixture.
• Maintainer records whether it affects config-health fixtures, field-report fixtures, consumer examples, docs only, or no code.

Notes

This is the second required external signal before a beta label can be reconsidered. Solo evidence and the trust packet improve confidence, but they do not close this issue.

[saagpatel]

Released v1.5.5 with a copy-paste external field-report request packet:

• Request packet: https://github.com/saagpatel/MCPAudit/blob/main/docs/EXTERNAL-FIELD-REPORT-REQUEST.md
• Public field-report template: https://github.com/saagpatel/MCPAudit/issues/new?template=field_report.md

Use this packet when asking a second, meaningfully different setup or consumer path for a redacted config-only report. This issue should stay open until the second acceptable external report is received and triaged.

[saagpatel]

Public outreach ready; updated for v1.13.1 and --redact.

Contributor packet: https://github.com/saagpatel/MCPAudit/blob/main/docs/EXTERNAL-FIELD-REPORT-REQUEST.md
Trust packet: https://github.com/saagpatel/MCPAudit/blob/main/docs/MCP-TRUST-PACKET.md

This second report should come from a meaningfully different setup or consumer path than #83, for example a different MCP client mix, OS, CI/dashboard consumer, or server shape.

Short ask to send:

Could you help validate MCPAudit beta readiness by running one config-only field report from a different MCP setup or consumer path?

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

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

`--redact` scrubs hostname, home-path usernames, and server names from shared artifacts. Please still redact credentials, private paths, internal hostnames, private URLs, customer names, and proprietary prompt/resource/tool/schema text.

This issue remains open until the second acceptable external report is received.

[saagpatel]

Outreach kit is now available on main:\n\n- Direct second-tester ask: https://github.com/saagpatel/MCPAudit/blob/main/docs/EXTERNAL-OUTREACH-MESSAGES.md#direct-ask-for-second-tester\n- Request packet: https://github.com/saagpatel/MCPAudit/blob/main/docs/EXTERNAL-FIELD-REPORT-REQUEST.md\n\nUse this issue for a second accepted external report from a meaningfully different setup or consumer path than #83. Solo evidence remains separate and does not close this issue.