Check npm and PyPI packages exist before install: versions, age, downloads, look-alikes.
Scored across 1 tool
There is only one tool, so there is nothing to confuse it with. Its name and description scope it precisely to pre-install package verification for npm and PyPI.
The single name 'notary_check_packages' follows a clean server-prefixed verb_noun pattern in snake_case. No mixed conventions exist because the surface is one tool.
A one-tool surface is thin even for a narrow domain; batch handling (up to 10 packages) offsets this somewhat. It is a focused micro-server rather than a clear mismatch, but it sits at the low end of the appropriate range.
The tool covers existence, version resolution, downloads, publish dates, deprecation/yank status, install scripts, typosquat distance, and similar-name suggestions—essentially the full verification lifecycle. Gaps are minor (no lockfile/SBOM bulk scan, no license or advisory data), and malware/vuln scanning is explicitly out of scope.
Use when the user or an agent is about to install or import npm or PyPI packages: before npm install or pip install, when adding lines to package.json or requirements.txt, or when a package name came from an AI answer, a tutorial or memory and may be invented. Looks each name up in the live registry and returns whether it exists, the latest version, whether a pinned version exists, weekly downloads, first and last publish dates, deprecation or yanked status, install-time scripts, whether the name is one or two typed characters from a well-known package, and real similar packages when the name does not exist. Example: {"packages":[{"ecosystem":"npm","name":"@anthropic/mcp-client"},{"ecosystem":"pypi","name":"requests","version":"2.32.3"}]}. Up to 10 packages per call; versions must be exact, not ranges. Not a malware or vulnerability scan: "ok" means it exists and nothing looked wrong.
Inputs: packages (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Check npm packages for typosquats, hallucinated names, install scripts and risky new releases.
Check npm/PyPI packages exist and that a function or method exists in an exact package version.
x402-gated safety checker for npm/PyPI packages before you npm install / pip install.
Detect npm download-pumping before adding a dependency: real usage vs inflated counter.
Add one secure layer between your agents and this server.