Package risk checks: maintenance, licence, advisories. Paid per call in USDC, no signup.
MCP tools for checking a package's maintenance status, licence, and security
advisories before you depend on it - package_risk, package_licence,
package_advisories. Paid per call in USDC on Base mainnet via x402.
No subscription, no API key. You pay from your own wallet, per call, only for what you use.
This is a thin client. The actual service is a stateless HTTP API at
x402-package-risk.x402-package-risk.workers.dev. This connector never sees,
holds, or forwards anyone else's funds - it only ever spends the wallet key
you configure below, and only when you call one of its tools.
You need an EVM wallet with a small amount of USDC on Base mainnet (calls cost $0.005-$0.01 each). Never use a wallet holding significant funds for an automated agent key - keep this one funded lightly.
Add to your MCP client config (Claude Desktop, Claude Code, Cursor, etc.):
{
"mcpServers": {
"package-risk": {
"command": "npx",
"args": ["-y", "@makosdav/package-risk-mcp"],
"env": {
"EVM_PRIVATE_KEY": "0xyour-private-key-here"
}
}
}
}
| Tool | Price | What it returns |
|---|---|---|
package_risk | $0.01 | Full verdict: maintenance, licence, advisories, deprecation |
package_licence | $0.005 | Licence expression and closed-source safety |
package_advisories | $0.005 | Open OSV advisories for the resolved version |
All three take system (npm/pypi/go/maven/cargo/nuget), name, and an
optional version.
402 Payment Required.@x402/fetch builds and signs a payment authorisation with your key.No approval prompt happens here beyond what your MCP client itself asks for - if you want per-call confirmation, configure that in your agent framework, not here.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @makosdav/package-risk-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-makosddavid-package-risk": {
"command": "npx",
"args": [
"-y",
"@makosdav/package-risk-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@makosdav/package-risk-mcpnpmio.github.makosdDavid/package-risk works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.