cf-package-check
Abandonment checks for WordPress, npm and PyPI packages, priced per call.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"cf-package-check": {
"url": "https://packages.cfsoft.us/mcp"
}
}
}Remote endpoints
https://packages.cfsoft.us/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢package_check(ecosystem, name)
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.
Input Schema
{
"type": "object",
"properties": {
"ecosystem": {
"type": "string",
"enum": [
"wordpress",
"npm",
"pypi"
]
},
"name": {
"type": "string",
"description": "npm package (\"express\", \"@scope/pkg\"), PyPI project (\"requests\"), or WordPress.org plugin slug (\"contact-form-7\")."
}
},
"required": [
"ecosystem",
"name"
],
"additionalProperties": false
}🟢package_sources
List the registry endpoints this service reads, the scoring rules and the cache policy. Free.
Input Schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Community
Evidence