Package Health Check

app.openkrillv1.0.0Updated Oct 3, 2026

Check an npm or Python package, or a package.json, for vulnerabilities and upkeep.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant check an npm or Python package, or a package.json file, for vulnerabilities and maintenance health.

What it does
This remote MCP server provides package health checking. According to its registry description, it checks an npm or Python package, or a package.json file, for vulnerabilities and upkeep. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when reviewing dependencies, auditing a project's packages, or deciding whether a package is safe and actively maintained. It fits dependency review and supply-chain checks during development.
Requirements
Runs as a remote streamable HTTP endpoint at packages.openkrill.app; no local runtime, package, environment variables, or headers are declared. No authentication is declared. Network access to the endpoint is required.
Before you install
The manifest declares no authentication, so consider what package names or package.json contents you send to a third-party endpoint. Results are advisory and should be verified before acting on them.

Installation

In SourceWeft

  1. Open Package Health Check 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.

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 3, 2026