Npm Trusted Publish Lint MCP server
Finds the credential in your release workflow that expires before your next release
A89/100grade A
Adoption
Growing
0 stars166 downloads/wk
Reviews
Write oneNobody has reviewed Npm Trusted Publish Lint yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Npm Trusted Publish Lint tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan6 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/npm-trusted-publish-lint on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add npm-trusted-publish-lint -- npx -y @readystack/npm-trusted-publish-lint
Npm Trusted Publish Lint: common questions
- Is Npm Trusted Publish Lint MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Npm Trusted Publish Lint safety report
- How do I install Npm Trusted Publish Lint?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Npm Trusted Publish Lint need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Npm Trusted Publish Lint maintained?
- The last commit was 2 days ago (2026-09-19). The latest release is v1.0.2.