Package check for coding agents (x402)

com.onrender.package-check-qy40Published by package-check-qy40.onrender.comOfficial publisherv0.4.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that checks PyPI and npm packages or whole lockfiles for CVEs, typosquats and an install verdict before an agent installs them.

What you can do
Check packages or lockfiles: one verdict per unique package, with line numbers where the format has them, covering whether a package exists, CVEs and typosquat risk, for requirements.txt, poetry.lock, uv.lock, Pipfile.lock, package-lock.json, pnpm-lock.yaml and yarn.lock formats. Run a free self-test: replay the published known-answer set of 11 cases against the live registries and return a score and sha256 so the check can be verified before paying.
When to use it
Use it when a coding agent is about to run pip install or npm install and you want a pre-install safety verdict on individual packages or an entire lockfile, and you want to confirm the checker works before spending on it.
Requirements
A remote streamable HTTP endpoint; no local runtime, account, API key or headers are declared. Payment is per package in USDC on Base via x402, so a wallet able to pay x402 charges is needed for paid checks; the self-test is free.
Before you install
Paid checks cost $0.002 USDC per package on Base through x402, so spending real funds requires a funded wallet and the per-package charge applies to lockfiles with many packages. The self-test is free and should be run first. Package names and lockfile contents are sent to the remote service.

Installation

In SourceWeft

  1. Open Package check for coding agents (x402) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.onrender.package-check-qy40%2Fpackage-check/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "package-check-for-coding-agents-x402": {
      "type": "http",
      "url": "https://package-check-qy40.onrender.com/mcp"
    }
  }
}

Tools

2

check_packages

Package check before pip/npm install (paid, x402)

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.

Parameterslimitlockfilepackagesinclude_devlockfile_format

selftest

Free self-test

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.

Parametersdetails

Version history

1
  1. v0.4.0LatestOct 25, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.