# MCPFax Dev Package Intelligence (remote · devpkg-intel.bowling-anthony.workers.dev)

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

- Trust score: 74/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `devpkg-intel.bowling-anthony.workers.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-mcpscores-dev-package-intel/devpkg-intel.md), [page](https://verifymcp.io/servers/com-mcpscores-dev-package-intel/devpkg-intel)

## Channel facts

- Endpoint: `https://devpkg-intel.bowling-anthony.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 770 tokens (~154/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MCPFax Dev Package Intelligence MCP server?

MCPFax Dev Package Intelligence is a hosted endpoint at https://devpkg-intel.bowling-anthony.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-mcpscores-dev-package-intel 'https://devpkg-intel.bowling-anthony.workers.dev/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "com-mcpscores-dev-package-intel": {
      "type": "http",
      "url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcpscores-dev-package-intel": {
      "type": "remote",
      "url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mcpscores-dev-package-intel --url 'https://devpkg-intel.bowling-anthony.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mcpscores-dev-package-intel:
    url: "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mcpscores-dev-package-intel": {
      "Transport": "http",
      "Url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mcpscores-dev-package-intel -t streamable-http -u 'https://devpkg-intel.bowling-anthony.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mcpscores-dev-package-intel": {
      "type": "http",
      "url": "https://devpkg-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `request_data` (~88 tokens)

Tell us what data you are looking for (free)

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.

Input parameters:

- `need` (string, required): What you are looking for.

### `demand_report` (~57 tokens)

What agents are asking for most (free)

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.

Input parameters:

- `days` (string): Window in days, default 30, max 90.

### `package_info` (~151 tokens)

Latest version and metadata for a package

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.

Input parameters:

- `ecosystem` (string, required): One of 'npm', 'pypi', 'crates' (aliases: node, python, rust).
- `name` (string, required): Package name, e.g. 'express', '@scope/pkg', 'requests', 'serde'.

### `package_vulnerabilities` (~152 tokens)

Known vulnerabilities for a package

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.

Input parameters:

- `ecosystem` (string, required): One of 'npm', 'pypi', 'crates'.
- `name` (string, required): Package name.
- `version` (string): Optional exact version, e.g. '4.17.20'. Narrows advisories to that version.

### `package_audit` (~140 tokens)

Should I add this dependency?

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.

Input parameters:

- `ecosystem` (string, required): One of 'npm', 'pypi', 'crates'.
- `name` (string, required): Package name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-mcpscores-dev-package-intel/devpkg-intel#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 74
- 2026-09-22: 73
- 2026-09-21: 73
- 2026-09-20: 73
- 2026-09-19: 72
- 2026-09-18: 72
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 65
- 2026-09-03: 65
- 2026-09-02: 64
- 2026-09-01: 64
- 2026-08-31: 63
- 2026-08-30: 63
- 2026-08-29: 62
- 2026-08-28: 62

## Common questions

### What is the MCPFax Dev Package Intelligence MCP server?

MCPFax Dev Package Intelligence is an MCP server listed in the public MCP registry as com.mcpscores/dev-package-intel. Is this dependency current, licensed, deprecated, or already carrying a CVE? This page covers its hosted endpoint (https://devpkg-intel.bowling-anthony.workers.dev/mcp).

### Is the MCPFax Dev Package Intelligence MCP server safe to use?

MCPFax Dev Package Intelligence scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MCPFax Dev Package Intelligence MCP server expose?

MCPFax Dev Package Intelligence exposes 5 tools: request_data, demand_report, package_info, package_vulnerabilities, package_audit. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.

### Does the MCPFax Dev Package Intelligence MCP server require authentication?

No. We connected to MCPFax Dev Package Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MCPFax Dev Package Intelligence MCP server still maintained?

MCPFax Dev Package Intelligence is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://devpkg-intel.bowling-anthony.workers.dev/mcp
- Website: https://mcpscores.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-mcpscores-dev-package-intel/devpkg-intel.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mcpscores-dev-package-intel/devpkg-intel.json
- HTML version of this page: https://verifymcp.io/servers/com-mcpscores-dev-package-intel/devpkg-intel