MCPFax Dev Package Intelligence MCP Server

by mcpscores Your server? Claim it

answering

MCPFax Dev Package Intelligence is answering right now. Last checked 14 min ago. It exposes 5 tools.

Is this dependency current, licensed, deprecated, or already carrying a CVE?

Uptime history 54 days of history · worst day 92%

54 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

78 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 9

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 August 2026. No other catalogue keeps this.

5 Sep a tool changed version

4 Sep 5 tools changed the parameters they ask for demand_report, package_audit, package_info and 2 more

31 Aug 3 tool descriptions were rewritten package_audit, package_info, package_vulnerabilities

Nothing serious here today

Today is the operative word: we check MCPFax Dev Package Intelligence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add dev-package-intel --transport http https://devpkg-intel.bowling-anthony.workers.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "dev-package-intel": {
      "url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.dev-package-intel]
url = "https://devpkg-intel.bowling-anthony.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "dev-package-intel": {
      "url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "dev-package-intel": {
      "url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

package

package_audit

One 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.

package_info

Look 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_vulnerabilities

Known 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.

demand

demand_report

FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.

request

request_data

FREE, 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.

Endpoints

URL	Transport	State	Latency	Checked
https://devpkg-intel.bowling-anthony.workers.dev/mcp	streamable-http	answering	72 ms	14 min ago

Alternatives to MCPFax Dev Package Intelligence

same job, measured the same way

npm Registry MCP Server

by yawlabs

npm registry MCP server — package intelligence, security audits, dependency analysis

429 installs/wk local only

Fintel Discovery — Financial Intelligence for AI Agents

by nikolayds

DEPRECATED — this server is no longer maintained.

local only

Package Intel MCP

by datakoot

Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.

6 tools answering

Dependency Health MCP

by ux-xd

Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates.

3 tools answering

Nekzus npm Sentinel MCP

by smithery

Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…

answering

Celmis

by constantinemakoid

Self-hosted code intelligence: cross-repo Q&A, dependency audits and PR review, over MCP

local only

ShadowGraph

by shadowalpha

Live outage status, internet dependencies and pay-per-call market intelligence for AI agents.

10 tools answering

Flyto Indexer

by chesterhsu

Code intelligence MCP server: impact analysis, dependency graphs, dead code detection.

local only

MCPFax Dev Package Intelligence — questions

Answers built from our own checks of this server.

What can MCPFax Dev Package Intelligence do?

It exposes 5 tools, read directly from the server on our last check. Among them: demand_report, package_audit, package_info, package_vulnerabilities, request_data. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is MCPFax Dev Package Intelligence working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 78 ms. The bar chart above shows every period we have measured.

How do I connect MCPFax Dev Package Intelligence?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MCPFax Dev Package Intelligence need an API key?

No. MCPFax Dev Package Intelligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MCPFax Dev Package Intelligence?

It answers our handshake in 78 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.