mcpbeat Sign in

License Boundary MCP Server

local only

License Boundary MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 52 installs a week from npm.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 135 · avg 15 · +21% w/w
a month agotoday
52
Installs / week
npm · license-boundary-mcp
—
Stars
on GitHub
—
Last commit
3 releases in 90 days
—
License
language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add license-boundary-mcp -- npx -y license-boundary-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "license-boundary-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "license-boundary-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.license-boundary-mcp]
command = "npx"
args = ["-y", "license-boundary-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "license-boundary-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "license-boundary-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "license-boundary-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "license-boundary-mcp"
      ]
    }
  }
}

Alternatives to License Boundary MCP

same job, measured the same way
Dependency License Change MCP
by mrfentmen

Compare local license evidence across two snapshots without returning package names, text,...

115 installs/wk local only
Dependency Drift MCP
by mrfentmen

Summarize local dependency manifest and lockfile drift without returning package names,...

119 installs/wk local only
Build Cache MCP
by mrfentmen

Summarize local build and cache footprint using size and age buckets without returning paths or...

114 installs/wk local only
Incident Timeline MCP
by mrfentmen

Summarize local log timeline gaps and severity counts without returning messages, IDs, paths, or...

55 installs/wk local only
Release Notes Forge MCP
by mrfentmen

Summarize local Git release shape without returning commit messages, paths, hashes, or remotes.

54 installs/wk local only
Test Shape MCP
by mrfentmen

Audit local test structure using aggregate assertions without returning test names, paths, or...

55 installs/wk local only
Runtime Support MCP
by mrfentmen

Summarize runtime declarations across local manifests and CI files without returning versions,...

49 installs/wk local only
Agent Residue Evidence
by fantasyce

Report local task-scoped test and build residue without cleaning resources.

local only

License Boundary MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for License Boundary MCP?
License Boundary MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package license-boundary-mcp was installed 52 times last week.
Is License Boundary MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect License Boundary MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls license-boundary-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use License Boundary MCP?
The npm package license-boundary-mcp was installed 52 times in the last week. Week over week that is +21%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.