Hardcoded Credential Audit MCP server
Open any config file and see every hardcoded credential — and every setting that quietly undoes your
A89/100grade A
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Hardcoded Credential Audit yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Hardcoded Credential Audit tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.3 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y @readystack/hardcoded-credential-audit on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add hardcoded-credential-audit -- npx -y @readystack/hardcoded-credential-audit
Hardcoded Credential Audit: common questions
- Is Hardcoded Credential Audit MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Hardcoded Credential Audit safety report
- How do I install Hardcoded Credential Audit?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Hardcoded Credential Audit need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Hardcoded Credential Audit maintained?
- The last commit was in the last day (2026-09-19). The latest release is v0.1.1.