Package check for coding agents (x402) MCP Server

by onrender-package-check-qy40 Your server? Claim it

not responding

Package check for coding agents (x402) is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Check PyPI/npm packages or a whole lockfile before install: CVEs, typosquats, verdict. 50 free.

Uptime history 15 days of history · worst day 0%

15 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

223 ms

Response time

average over 24h

open, no key

Access

streamable-http

Package check for coding agents (x402) does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add package-check --transport http https://package-check-qy40.onrender.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://package-check-qy40.onrender.com/mcp

~/.codex/config.toml

[mcp_servers.package-check]
url = "https://package-check-qy40.onrender.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "package-check": {
      "url": "https://package-check-qy40.onrender.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "package-check": {
      "type": "http",
      "url": "https://package-check-qy40.onrender.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

packages

check_packages

Before your agent runs pip install or npm install, check a package list or a whole lockfile (requirements.txt, poetry.lock, uv.lock, Pipfile.lock, package-lock.json, pnpm-lock.yaml, yarn.lock; one verdict per unique package, with line numbers where the format has them). Per package: does it exist, age, releases, downloads, known vulnerabilities (OSV) for the given or latest version, typosquat and slopsquat signals, install scripts; verdict ok, caution or block with reasons. PyPI and npm. A clean ok is not a guarantee. Costs $0.002 USDC per package on Base via x402: the first call without payment returns the payment requirements; pay with an x402-capable MCP client (_meta['x402/payment']) or call POST https://package-check-qy40.onrender.com/check over HTTP x402. Free trial: the first 50 packages per payer wallet are free; sign as usual, the server verifies the signature and does not settle; the result shows free_trial_remaining. About 50: the counter is in memory and resets on restart.

selftest

selftest

Free. Replays the published known-answer set v1 (11 cases) against the live registries and returns score and sha256, so you can verify the check before paying.

Endpoints

URL	Transport	State	Latency	Checked
https://package-check-qy40.onrender.com/mcp	streamable-http	answering	223 ms	2 min ago

Alternatives to Package check for coding agents (x402)

same job, measured the same way

pkgproof

by pkgproof

Verify an npm or PyPI package before install: advisories, install scripts, typosquats, repository.

73 installs/wk local only

Attestari

by attestari

Attestari's verdict on an npm or PyPI package version, asked before an agent installs it.

281 installs/wk answering

PackageGuard

by dankaten

x402-gated safety checker for npm/PyPI packages before you npm install / pip install.

1 tools answering

Vdb

by ai-vdb

Check packages for CVEs, slopsquatting, and CISA KEV before your AI agent installs them.

215 installs/wk 7 tools answering

Presend MCP Server

by presendapp

Before an AI agent installs an npm/PyPI package: typosquat, vulnerability and existence checks.

40 tools answering

pkg-oracle — Dependency Trust Oracle

by julian-martin89

Blocks typosquatted or hallucinated npm/PyPI packages before an AI agent installs them.

1 tools answering

Package Guard MCP

by mlawsonking

Supply-chain guard for AI coding agents: verify packages, check vulns/malware, detect typosquats.

73 installs/wk local only

alalanet — check before you pay

by alalanet

Check packages, MCP servers and x402 endpoints before agents install or pay. Signed.

23 tools answering

Package check for coding agents (x402) — questions

Answers built from our own checks of this server.

What can Package check for coding agents (x402) do?

It exposes 2 tools, read directly from the server on our last check. Among them: check_packages, selftest. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Package check for coding agents (x402) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 223 ms. The bar chart above shows every period we have measured.

The registry lists Package check for coding agents (x402) as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Package check for coding agents (x402)?

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 is a remote server, so there is nothing to install — the client connects to the address.

Does Package check for coding agents (x402) need an API key?

No. Package check for coding agents (x402) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.