All servers · Agent payments (x402)
Package check for coding agents (x402)
com.onrender.package-check-qy40/package-check · v0.4.0
New (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Check PyPI/npm packages or a whole lockfile before install: CVEs, typosquats, verdict. 50 free.
Connect
streamable-http · https://package-check-qy40.onrender.com/mcp
claude mcp add --transport http package-check https://package-check-qy40.onrender.com/mcp{
"mcpServers": {
"package-check": {
"url": "https://package-check-qy40.onrender.com/mcp"
}
}
}Tools as reported by the server
check_packagesBefore 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, aselftestFree. 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.
Website · JSON · Text for agents · Registry updated 2026-10-24