Package Health Check
v1.1.0Check an npm or Python package, or a package.json, for vulnerabilities and upkeep.
Endpoint health
online- Last checked
- 11/20/2026, 5:17:45 AM
- Latency
- 299 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:app.openkrill%2Fpackages
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"app.openkrill/packages": {
"url": "https://packages.openkrill.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
6 shown · authentication unknown
Check a package's health
check_package
Use this when the user asks whether an npm or PyPI package is vulnerable, maintained, deprecated or safe to use, or what license it has: "is lodash 4.17.15 vulnerable?", "is this npm package maintained?", "what license is this package?", "safer alternative to request". Pass the public package name, ecosystem (npm or pypi) and a version if the user gave one; otherwise the latest is checked. Returns the known vulnerabilities of that version with severity and fixed version, the license, any deprecation notice, last release date, releases in the last year, weekly downloads (npm) and dependents. It does not pick alternatives: for a deprecated or stale package, suggest candidates and check each one with this tool.
Schema valid · SHA-256 f49ec8f676b0…
View input schema
{ "type": "object", "properties": { "name": { "type": "string", "minLength": 1, "maxLength": 214, "pattern": "^(@[A-Za-z0-9._~-]+/)?[A-Za-z0-9._~-]+$", "description": "Public package name, such as \"lodash\", \"@types/node\" or \"requests\"" }, "ecosystem": { "type": "string", "enum": [ "npm", "pypi" ], "description": "npm for JavaScript packages (the default), pypi for Python packages" }, "version": { "type": "string", "minLength": 1, "maxLength": 64, "pattern": "^[0-9A-Za-z][0-9A-Za-z.+!_-]*$", "description": "Exact version, such as \"4.17.15\". Omit to check the latest." } }, "required": [ "name" ], "additionalProperties": false, "examples": [ { "name": "lodash", "ecosystem": "npm", "version": "4.17.15" } ] }Check package.json for vulnerabilities
check_package_json
Use this when the user asks to check their package.json, or the dependencies of a project, for known vulnerabilities: "check my package.json for known vulnerabilities". Pass the text of the package.json; only the names and versions in dependencies, devDependencies and optionalDependencies are read, nothing else in the file is used or kept, and nothing is stored. Do not ask for source code or tokens. Checks up to 150 npm dependencies at the version each names (ranges at their lowest version) and returns the vulnerable ones, most severe first, with the fixed version. Dependencies without an exact version (tags, urls, workspaces) are listed as skipped.
Connections
streamable-http
https://packages.openkrill.app/mcp