License Sentinel MCP server
Audit Python and npm dependency licenses before you ship, judged against how you distribute.
A92/100grade A
Adoption
New
1 stars
Reviews
Write oneNobody has reviewed License Sentinel yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
License Sentinel tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · 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 6 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add license-sentinel -- uvx license-sentinel
License Sentinel: common questions
- Is License Sentinel MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the License Sentinel safety report
- How do I install License Sentinel?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does License Sentinel need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is License Sentinel maintained?
- The last commit was 6 days ago (2026-09-14). The latest release is v0.1.0.