MCP.Market

Package Intel MCP server

by adam121393·io.github.adam121393/package-intel·v1.1.1
No reviews yet

npm, PyPI & crates.io health, vulns and dependency graphs. Runs locally, no API key.

C68/100grade C
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
C68/100

full report

Adoption
New

0 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed Package Intel yet.

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

Package Intel tools (6)

write = sends, deletes, buys or posts

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

  • package_batch_health

    Score up to 50 packages in one call \u2014 use this to audit an entire package.json, requirements.txt or Cargo.toml at once instead of calling package_health repeatedly. Costs $0.02 in USDC per call.

  • package_deps

    Get the dependency graph for an npm, PyPI or crates.io (Rust) package: direct and transitive dependencies with versions and counts, with deprecated direct dependencies flagged. Free, no payment required.

  • package_downloads

    Get download counts for an npm, PyPI or crates.io (Rust) package over a time range. Free, no payment required.

  • package_health

    Get a 0-100 health/risk score for an npm, PyPI or crates.io (Rust) package, with maintenance, popularity, security, and freshness sub-scores plus a rationale. Use this to decide whether a dependency is safe to adopt. Costs $0.01 in USDC per call.

  • package_snapshot

    Get a consolidated snapshot of an npm, PyPI or crates.io (Rust) package: latest version, license, description, repository, weekly downloads, maintainers, last publish date, and deprecation status. Free, no payment required.

  • package_vulns

    List known vulnerabilities (OSV.dev) for an npm, PyPI or crates.io (Rust) package. Pass a version to scope results to that version; omit it to see every advisory ever filed against the package. Free, no payment required.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

1 medium
  • Code scan2 source files scanned20/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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 40 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    dist/server.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Package Intel compares

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

Safety score
68/100
higher than 30% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
35
more than 25% of 12,191 servers with a package

What its tools let an agent do: 6 read

Install Package Intel in Claude Code, Cursor or VS Code

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

claude mcp add package-intel -- npx -y package-intel-mcp
Add to Cursor

What the publisher says

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

Package & Dependency Intelligence API (x402)

A pay-per-call API selling npm, PyPI and crates.io (Rust) package health, dependency-graph, and vulnerability data to AI coding agents over the x402 payment protocol — plus an MCP server so agents in Claude Desktop/Cursor can call it and pay automatically.

Defaults to Base Sepolia testnet via the free public facilitator. Going to mainnet is an explicit config change (see Going to mainnet).

Endpoints

Raw passthrough of the upstream sources is free: npm, PyPI, crates.io, OSV and deps.dev are themselves free and unauthenticated, so charging for a relay of them prices against zero. What gets charged for is the consolidation — the score.

:ecosystem is npm, pypi or crates. Also unpaid: /healthz, /v1/sample (canned example response), /.well-known/x402 (discovery manifest).

Free routes are rate limited to 60/min and 2000/day per caller — a runaway agent loop is how we would get our egress IP blocked by npm or OSV. Paid routes are exempt; their price is the limiter. Exceeding a limit returns 429 with Retry-After.

Tier, price, description, and discovery metadata all come from src/catalog.ts — edit there and the payment middleware, rate limiter, manifest, and Bazaar declarations stay in sync. tier is a required discriminant, so a new endpoint cannot default into being free.

Trusting the caller's address

The rate limiter counts per client IP, but the service sits behind a Worker proxy and a tunnel, so every request arrives from the same address. The proxy forwards the real one as x-stable-ip signed with PROXYSECRET**, and the origin honours it only when the secret matches. Anything else — wrong secret, no secret, or a request straight to the tunnel hostname — shares a single bucket. Without that signature a caller could forge a fresh address per request, or skip the proxy, and get unmetered upstream fan-out.

Set the same value in both places:

# .env for the origin, plus:
npx wrangler secret put PROXY_SECRET

The server warns at startup if it is missing on mainnet.

Local setup (testnet)

npm install
npm run gen-wallet

gen-wallet prints two testnet-only keypairs — never fund these with real assets:

script to simulate a paying agent).

  • Seller — put its address in .env as PAY_TO (where payments land).
  • Buyer — put its private key in .env as BUYERPRIVATEKEY (used by the test

Copy .env.example to .env and fill those in. Then fund the buyer with Base Sepolia USDC at faucet.circle.com (select Base Sepolia; no account needed). No testnet ETH is required — x402's exact scheme uses EIP-3009, so the buyer only signs off-chain and the facilitator pays gas.

npm run dev

Verify: curl http://localhost:4021/healthz → 200, and curl -i http://localhost:4021/v1/health/npm/express → 402 with payment instructions.

Test the payment flow

npm run test-buyer                              # GET /v1/health/npm/express (default)
npm run test-buyer -- /v1/deps/npm/express
npm run test-buyer -- /v1/batch

On Git Bash/Windows, prefix with MSYSNOPATHCONV=1 so the leading / isn't rewritten into a Windows path.

A request for a nonexistent package returns 404 without charging — the x402 middleware skips settlement entirely on any 4xx/5xx response, so failures are free.

Shortened. The full README is on GitHub.

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

Package Intel: common questions

Is Package Intel MCP server safe?
With care: it is graded C, so read the findings first (68/100). Read the Package Intel safety report
How do I install Package Intel?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Package Intel need an API key?
Yes. The registry entry asks for X402_PRIVATE_KEY.
Is Package Intel maintained?
The last commit was 81 days ago (2026-08-14). The latest release is v1.1.1.
How does Package Intel compare with other MCP servers?
safety score 68/100 (higher than 30% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.