All servers · Security · Payments & accounting
MCPFax Dev Package Intelligence
com.mcpscores/dev-package-intel · v1.0.2
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 5 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Is this dependency current, licensed, deprecated, or already carrying a CVE?
Connect
streamable-http · https://devpkg-intel.bowling-anthony.workers.dev/mcp
claude mcp add --transport http dev-package-intel https://devpkg-intel.bowling-anthony.workers.dev/mcp{
"mcpServers": {
"dev-package-intel": {
"url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
}
}
}Tools as reported by the server
request_dataFREE, no payment. Describe in your own words the data you are trying to buy — anything, not just packages — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, onldemand_reportFREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.package_infoLook up a package in npm, PyPI or crates.io: latest version, licence, whether it is deprecated or yanked, when it was last published, dependency count and repository. Use before writing a dependency line, or to check whether a pinned version is behind. Registries answer with hundreds of kilobytes; tpackage_vulnerabilitiesKnown security advisories for a package from OSV, the open advisory database. Returns advisory ids, severity, summary and the versions that fix each one. Pass 'version' to ask only about the version you are about to install; omit it to see advisories affecting any version. Use before pinning a depenpackage_auditOne call that answers whether a dependency is safe to add: latest version, licence, deprecation, advisories affecting the current version, how long since the last release, and a verdict with the specific concerns found. Prefer this over calling package_info and package_vulnerabilities separately — i
Website · JSON · Text for agents · Registry updated 2026-08-31