MCPFax Dev Package Intelligence
com.mcpscores/dev-package-intel · 1.0.2
Is this dependency current, licensed, deprecated, or already carrying a CVE?
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://devpkg-intel.bowling-anthony.workers.dev/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- com.mcpscores/dev-package-intel 1.0.2
- Handshake time
- 88 ms
- HTTP status
- 200
The tools it lists (5, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
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, only the words of the request.
demand_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; this returns only the facts that decide the question. Costs $0.005 USDC per call via x402 on Base.
package_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 dependency or when auditing a lockfile. Costs $0.008 USDC per call via x402 on Base.
package_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 — it is one payment instead of two and applies the judgement. A clean verdict means nothing was found in these sources, not that the package is guaranteed safe. Costs $0.01 USDC per call via x402 on Base.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.mcpscores/dev-package-intel, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 38 days ago. The registry entry · mcpscores.com