Local MCP capabilities provider for Expo
MCPFax Dev Package Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Is this dependency current, licensed, deprecated, or already carrying a CVE?
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcpfax-dev-package-intelligence https://devpkg-intel.bowling-anthony.workers.dev/mcp
# 2 — ask your agent for something these tools do
# request_data, demand_report, package_info and 2 more
MCPFax Dev Package Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mcpfax-dev-package-intelligence https://devpkg-intel.bowling-anthony.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | yes | What you are looking for. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | string | no | Window in days, default 30, max 90. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ecosystem | string | yes | One of 'npm', 'pypi', 'crates' (aliases: node, python, rust). |
| name | string | yes | Package name, e.g. 'express', '@scope/pkg', 'requests', 'serde'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ecosystem | string | yes | One of 'npm', 'pypi', 'crates'. |
| name | string | yes | Package name. |
| version | string | no | Optional exact version, e.g. '4.17.20'. Narrows advisories to that version. |
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ecosystem | string | yes | One of 'npm', 'pypi', 'crates'. |
| name | string | yes | Package name. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MCPFax Dev Package Intelligence or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.2.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish MCPFax Dev Package Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.