Skip to main content
Glama
package-risk MCP connector

package-risk MCP connector

by makosdDavid

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.

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.

Related MCP server: agent-toolkit-mcp

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

  1. Your agent calls a tool.

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

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

  4. 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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Marketplace MCP for paid HTTP APIs. Pay per call in USDC on Base via the open x402 standard — non-custodial. 13 tools for discovery, buying, and publishing APIs.
      7
      52 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides coding agents with 19 pay-per-call developer utilities, npm supply-chain security checks, and Base blockchain lookups, paid via USDC on Base using x402. No API key needed—payment acts as authentication.
      64 npm
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to query whether a WordPress plugin, npm package, or PyPI project looks abandoned, returning a live abandonment-risk score, status, and the registry signals behind it, plus raw registry, GitHub, and version history detail. Calls are paid per request in USDC via x402, with free discovery and source-listing tools.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access pay-per-call onchain and URL safety APIs over MCP, covering transaction explanations, token approval checks, address inspection, contract risk heuristics, URL safety, gas snapshots, ENS resolution, calldata decoding, and wallet portfolio data. Payments are handled per call in USDC on Base via x402, with no signup or API key required.
      1
      MIT