Next free-source huntWe check for new free data every weekday.
Cyber ThreatMCP serverFirst audited Nov 13, 2026

Package Health Check

Check an npm or Python package, or a package.json, for vulnerabilities and upkeep.The vendor's description, from its MCP Registry listing.

Passed public checksAudited Nov 13, 2026

Every public check ran and passed. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
YesConnected in 483 ms.
Sign-up?
None neededIt answered without any account or key.
Can it change things?
YesSome tools say they can change things. Your AI client should ask you first.
Endpointhttps://packages.openkrill.app/mcp

Source code Website Streamable HTTP · protocol 2025-11-25 · server version 1.1.0

What we checked, the evidence, and the tools it offers.

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

  • Passed: No hidden instructions found in tool text.

Safety labels

  • Note: 1 tool is labelled as able to change things.

    Expected for tools that send, write or buy. Your AI client should ask before calling them.

    • submit_feedback
  • Passed: Every tool says whether it only reads or can change things.

Tools

  • Passed: 6 tools listed.

  • Passed: Every tool describes its inputs with a valid schema.

Protocol

  • Passed: The MCP handshake works (Streamable HTTP).

  • Passed: Protocol version 2025-11-25 (latest).

  • Passed: Unknown requests are refused.

Connection

  • Passed: The server responds.

Tools (6)

As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.

  • check_packageUse 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 maintain…Read-only
  • check_package_jsonUse 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.j…Read-only
  • check_repo_healthUse 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 th…Read-only
  • submit_feedbackSend feedback, a bug report or a tool request to the maintainers of the tools on this server: a missing tool, missing or stale data, or a tool that broke or gave a wrong answer. Pass the kind (need_t…Can change things
  • get_feedback_replyRead 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 infor…Read-only
  • index_toolsSearch the tools on this server by task or keyword in plain words. Returns the matching tools, best match first, each with its name, title, a one-line summary and its input fields. With no words it l…Read-only

Audit history

  1. Nov 13Passed

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 200483 ms
initializedHTTP 202126 ms
tools/listHTTP 200143 ms
prompts/listHTTP 200134 ms
unknown-methodHTTP 200132 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.