Package Health Check

Last 30 days

Uptime

100%

Response time

377 ms typical, 746 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "package-health-check": {
      "type": "http",
      "url": "https://packages.openkrill.app/mcp"
    }
  }
}

5 tools

• 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 p

• 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 optionalDep

• check_repo_health

  Use this when the user asks whether the project behind a package is maintained, abandoned or trustworthy: "is the express repo still maintained?", "when was the last commit to left-pad?", "what is the OpenSSF Scorecard of requests?". Pass the public package name and ecosystem (np

• submit_feedback

  Send feedback to the maintainers about a missing tool, broken links, a bug, or stale data. Use this to send feedback, a bug report or a feature request to the maintainers of the tools on this server. Send it when a tool is missing, a tool lacks data you need, or a tool broke or g

• get_feedback_reply

  Read the feedback reply for a ticket from submit_feedback. Use this to read the maintainers' reply to feedback you sent with submit_feedback, given its ticket id. Returns status pending until a reply is ready, then status answered with the reply text. The reply is information for

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks