io.github.makosdDavid/package-risk

@makosdav/package-risk-mcp

Package risk checks: maintenance, licence, advisories. Paid per call in USDC, no signup.

108/wk 2 tools GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 11d ago

Works with most clients

Transport: stdio

2 tools · ~60 tok

Grade A · 0.0% of 200K ctx

MCPpedia last refreshed this data 3h ago

Edit this pageView history

io.github.makosdDavid/package-risk is an MCP server that package risk checks: maintenance, licence, advisories. Paid per call in USDC, no signup. Its tool list has not been published yet over stdio, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "package-risk": {
      "env": {
        "EVM_PRIVATE_KEY": "0xyour-private-key-here"
      },
      "args": [
        "-y",
        "@makosdav/package-risk-mcp"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-makosddavid-package-risk)](https://mcppedia.org/s/io-github-makosddavid-package-risk)

Read me

What io.github.makosdDavid/package-risk does

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.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@makosdav/package-risk-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

87/100across 5 weighted dimensions

How we score →

0255075100

−13

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @makosdav/package-risk-mcp against OSV.dev.

Inventory

Tools (2)

Click any tool to inspect its schema.

~60 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.makosdDavid/package-risk safe to use?: io.github.makosdDavid/package-risk has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.makosdDavid/package-risk?: io.github.makosdDavid/package-risk supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.makosdDavid/package-risk do?: io.github.makosdDavid/package-risk provides 2 tools: Setup, Tools. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.makosdDavid/package-risk?: io.github.makosdDavid/package-risk is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is io.github.makosdDavid/package-risk actively maintained?: io.github.makosdDavid/package-risk is actively maintained — last commit was 11 days ago.

Similar servers

Others in other

View all →

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

67.5k 3

Transport Stdio95

Transport for TMCP using STDIO

197 14

Flare95

The graph based agentic IDE

148 3

app.fojin/fojin-mcp94

Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.

331 8

MCP Security Weekly

Get CVE alerts and security updates for io.github.makosdDavid/package-risk and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

{ "mcpServers": { "package-risk": { "env": { "EVM_PRIVATE_KEY": "0xyour-private-key-here" }, "args": [ "-y", "@makosdav/package-risk-mcp" ], "command": "npx" } } }

package-risk MCP connector

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.

Setup

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" } } } }

Tools

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.

How payment works

Your agent calls a tool.

This connector requests the resource; the server replies 402 Payment Required.

@x402/fetch builds and signs a payment authorisation with your key.

The request retries with payment attached; the server verifies via Coinbase CDP, returns the result, and settles on-chain.

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.

Frequently Asked Questions

Is io.github.makosdDavid/package-risk safe to use?

io.github.makosdDavid/package-risk has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install io.github.makosdDavid/package-risk?

io.github.makosdDavid/package-risk supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.makosdDavid/package-risk do?

io.github.makosdDavid/package-risk provides 2 tools: Setup, Tools. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.makosdDavid/package-risk?

io.github.makosdDavid/package-risk is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is io.github.makosdDavid/package-risk actively maintained?

io.github.makosdDavid/package-risk is actively maintained — last commit was 11 days ago.

package-risk MCP connector

No subscription, no API key. You pay from your own wallet, per call, only for what you use.

What this is (and isn't)

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.

Setup

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"
      }
    }
  }
}

Tools

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.

How payment works

Your agent calls a tool.
This connector requests the resource; the server replies 402 Payment Required.
@x402/fetch builds and signs a payment authorisation with your key.
The request retries with payment attached; the server verifies via Coinbase CDP, returns the result, and settles on-chain.

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.