Skip to content

io.github.cfgenius145-sketch/cf-package-check

by cfgenius145-sketch · remote · no sign-in to list tools · v1.0.0 · published by GitHub user cfgenius145-sketch

Abandonment checks for WordPress, npm and PyPI packages, priced per call.

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http cf-package-check https://packages.cfsoft.us/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 1Claude Code: ask
  • package_checkCheck whether a WordPress.org plugin, npm package or PyPI project is abandoned.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check whether a WordPress.org plugin, npm package or PyPI project is abandoned. Costs $0.02 per call via x402. Returns status (active, stale, abandoned, deprecated or closed), a 0-100 abandonment-risk score, months since the last update, the latest release, and the signals behind the score. Signals, not a verdict: check the project before deciding.

    Annotations the server declares

    • readOnlyHint: true
Only reads 1Claude Code: allow
  • package_sourcesList the registry endpoints this service reads, the scoring rules and the cache policy.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the registry endpoints this service reads, the scoring rules and the cache policy. Free.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http cf-package-check https://packages.cfsoft.us/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__cf-package-check__package_sources"
    ],
    "ask": [
      "mcp__cf-package-check__package_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as cf-package-check. Review it before you use it.