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

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

- Trust score: 53/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `package.selflabbs.com`: 53/100 (this document), [markdown](https://verifymcp.io/servers/selflabbs-package-intel-mcp/package.md), [page](https://verifymcp.io/servers/selflabbs-package-intel-mcp/package)

## Channel facts

- Endpoint: `https://package.selflabbs.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http selflabbs-package-intel-mcp https://package.selflabbs.com/mcp
```

### Codex

```toml
[mcp_servers.selflabbs-package-intel-mcp]
url = "https://package.selflabbs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "selflabbs-package-intel-mcp": {
      "type": "remote",
      "url": "https://package.selflabbs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add selflabbs-package-intel-mcp --url https://package.selflabbs.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  selflabbs-package-intel-mcp:
    url: "https://package.selflabbs.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "selflabbs-package-intel-mcp": {
      "type": "http",
      "url": "https://package.selflabbs.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-07-31 (score 53, 0)

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

### 2026-07-30 (score 53, 0)

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

### 2026-07-29 (score 53, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] DNSSEC: fail → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security improvement] HTTPS: unverified → pass
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-28 (score 53, +1)

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

### 2026-07-27 (score 52, +1)

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

### 2026-07-26 (score 51)

First indexed and scored.

## MCP tools (6)

### `package_info` (~75 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)
- `name` (string, required): Package/crate name

### `package_versions` (~69 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)
- `limit` (integer)
- `name` (string, required)

### `package_downloads` (~59 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)
- `name` (string, required)

### `package_dependencies` (~79 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)
- `name` (string, required)
- `version` (string): Optional; defaults to the latest/default version

### `package_health` (~86 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)
- `name` (string, required)

### `package_search` (~57 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)
- `limit` (integer)
- `query` (string, required)

## Diagnostics

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

## Score history

- 2026-08-03: 53
- 2026-08-02: 53
- 2026-08-01: 53
- 2026-07-31: 53
- 2026-07-30: 53
- 2026-07-29: 53
- 2026-07-28: 53
- 2026-07-27: 52
- 2026-07-26: 51

## Links

- Remote endpoint: https://package.selflabbs.com/mcp
- Repository: https://github.com/selflabbs/package-intel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/selflabbs-package-intel-mcp/package/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/selflabbs-package-intel-mcp/package/changelog.json
- HTML version of this page: https://verifymcp.io/servers/selflabbs-package-intel-mcp/package