A remote MCP endpoint that checks whether WordPress, npm and PyPI packages appear abandoned, priced per call.
What you can do
This server exposes a remote MCP endpoint at packages.cfsoft.us. According to its registry description, it performs abandonment checks for WordPress, npm and PyPI packages. No tool list is published, so the exact tool names and parameters are not documented here. Each check is billed per call.
When to use it
Consider it when an assistant needs to assess whether a WordPress plugin, npm package or PyPI package is still maintained, for example before adding a dependency or reviewing an existing one. It is less useful if you need general package metadata or vulnerability data rather than abandonment signals.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to packages.cfsoft.us. No authentication, environment variables or headers are declared in the manifest, and no local runtime or package install is needed.
Before you install
Usage is priced per call, so repeated checks can incur charges; confirm the pricing and any spending limits before connecting. The manifest declares no authentication, so treat the endpoint as unverified and avoid sending sensitive data. The registry description is the only documentation available, and no tool list is published.
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.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.cfgenius145-sketch%2Fcf-package-check/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersnamerequiredecosystemrequired
package_sources
Sources and scoring method
List the registry endpoints this service reads, the scoring rules and the cache policy. Free.
Takes no parameters.
Version history
1
v1.0.0LatestSep 16, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.