License Boundary MCP server

by mrfentmen·io.github.mrfentmen/license-boundary-mcp·v1.0.0

No reviews yet

Summarize local license evidence and uncertainty without returning package names, license text,...

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed License Boundary yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

License Boundary tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

inspect_license_boundary
Summarize local license evidence and uncertainty without returning package names, license text, paths, or source.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan8 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 85 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How License Boundary compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 1; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read

Install License Boundary in Claude Code, Cursor or VS Code

Runs npx -y license-boundary-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add license-boundary-mcp -- npx -y license-boundary-mcp

Add to Cursor

What the publisher says

From the License Boundary repository's README, as published. We do not edit it. Read it on GitHub

license-boundary-mcp

License Boundary summarizes local license evidence before a release. It classifies common license markers and highlights unknown evidence without pretending to provide legal advice.

Quick start

npm install
npm test
npm start

Call inspectlicenseboundary with a bounded project path.

Privacy and limits

The server reads license files and recognized manifests, but only returns aggregate categories. It never returns license text, package names, paths, or source. Classification is intentionally conservative.

Nothing above is checked by us. What we check is on the safety report.

License Boundary: common questions

Is License Boundary MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the License Boundary safety report
How do I install License Boundary?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does License Boundary need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is License Boundary maintained?: The last commit was 87 days ago (2026-08-09). The latest release is v1.0.0.
How does License Boundary compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.