# Package Intel MCP (remote · package.datakoot.com)

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

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

## Components

- remote · `package.datakoot.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-datakoot-npm-pypi-crates-packages/package.md), [page](https://verifymcp.io/servers/com-datakoot-npm-pypi-crates-packages/package)

## Channel facts

- Endpoint: `https://package.datakoot.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## 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-27.

- **Endpoint Security**: 51/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 6 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 683 tokens (~113/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Package Intel MCP server?

Package Intel MCP is a hosted endpoint at https://package.datakoot.com/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-datakoot-npm-pypi-crates-packages 'https://package.datakoot.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-datakoot-npm-pypi-crates-packages": {
      "url": "https://package.datakoot.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-datakoot-npm-pypi-crates-packages": {
      "type": "http",
      "url": "https://package.datakoot.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-datakoot-npm-pypi-crates-packages]
url = "https://package.datakoot.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-datakoot-npm-pypi-crates-packages": {
      "type": "remote",
      "url": "https://package.datakoot.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-datakoot-npm-pypi-crates-packages --url 'https://package.datakoot.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-datakoot-npm-pypi-crates-packages:
    url: "https://package.datakoot.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-datakoot-npm-pypi-crates-packages": {
      "Transport": "http",
      "Url": "https://package.datakoot.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-datakoot-npm-pypi-crates-packages -t streamable-http -u 'https://package.datakoot.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-datakoot-npm-pypi-crates-packages": {
      "type": "http",
      "url": "https://package.datakoot.com/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-26 (score 73, +1)

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

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

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

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

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

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

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

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

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

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

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

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

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

### 2026-09-13 (score 67, +1)

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

## MCP tools (6)

### `package_info` (~91 tokens)

Get core metadata for a package: latest version, description, license, homepage, source repository, maintainers, and whether it is deprecated. Use before an agent installs or recommends a dependency. Ecosystems: npm, pypi, cargo.

Input parameters:

- `ecosystem` (string, required): Package registry to look in. One of: npm, pypi, cargo.
- `name` (string, required): Package/crate name

### `package_versions` (~116 tokens)

List recent released versions of a package with release dates (most recent first). Helps an agent pick a version or check how actively it is maintained. Ecosystems: npm, pypi, cargo.

Input parameters:

- `ecosystem` (string, required): Package registry to look in. One of: npm, pypi, cargo.
- `limit` (integer): Maximum number of results to return.
- `name` (string, required): Exact package name as published in that registry, e.g. express for npm, requests for pypi, serde for cargo.

### `package_downloads` (~100 tokens)

Get popularity/download statistics for a package (recent download counts). Useful for judging how widely used and battle-tested a dependency is. Ecosystems: npm, pypi, cargo.

Input parameters:

- `ecosystem` (string, required): Package registry to look in. One of: npm, pypi, cargo.
- `name` (string, required): Exact package name as published in that registry, e.g. express for npm, requests for pypi, serde for cargo.

### `package_dependencies` (~120 tokens)

List the direct dependencies of a specific package version (defaults to latest), via deps.dev. Lets an agent understand what a package pulls in before adding it. Ecosystems: npm, pypi, cargo.

Input parameters:

- `ecosystem` (string, required): Package registry to look in. One of: npm, pypi, cargo.
- `name` (string, required): Exact package name as published in that registry, e.g. express for npm, requests for pypi, serde for cargo.
- `version` (string): Optional; defaults to the latest/default version

### `package_health` (~127 tokens)

A composite trust/health check for a package an agent is considering: latest-release recency, deprecation status, license present, maintainer count, dependency count, and any known security advisories (via deps.dev). Returns a summary an agent can act on. Ecosystems: npm, pypi, cargo.

Input parameters:

- `ecosystem` (string, required): Package registry to look in. One of: npm, pypi, cargo.
- `name` (string, required): Exact package name as published in that registry, e.g. express for npm, requests for pypi, serde for cargo.

### `package_search` (~90 tokens)

Search for packages by keyword and get the top matches with descriptions. Supported ecosystems: npm and cargo (PyPI has no public search API).

Input parameters:

- `ecosystem` (string, required): Package registry to look in. One of: npm, pypi, cargo.
- `limit` (integer): Maximum number of results to return.
- `query` (string, required): Free-text search terms, matched against package names and descriptions.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-datakoot-npm-pypi-crates-packages/package#diagnostics

## Score history

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

## Common questions

### What is the Package Intel MCP server?

Package Intel MCP is listed in the public MCP registry as com.datakoot/npm-pypi-crates-packages. Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys. This page covers its hosted endpoint (https://package.datakoot.com/mcp).

### Is the Package Intel MCP server safe to use?

Package Intel MCP scores 73 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 Package Intel MCP server expose?

Package Intel MCP exposes 6 tools: package_info, package_versions, package_downloads, package_dependencies, package_health, package_search. Their descriptions and schemas cost roughly 644 tokens of context every time the server is loaded.

### Does the Package Intel MCP server require authentication?

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

### Is the Package Intel MCP server still maintained?

Package Intel MCP is still listed as active in the MCP registry. We last reached this channel on 27 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://package.datakoot.com/mcp
- Repository: https://github.com/datakoot/package-intel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-datakoot-npm-pypi-crates-packages/package.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-datakoot-npm-pypi-crates-packages/package.json
- HTML version of this page: https://verifymcp.io/servers/com-datakoot-npm-pypi-crates-packages/package