Package Intel MCP
REMOTE · PACKAGE.SELFLABBS.COM · SCANNED AUG 3
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Available components
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. How we score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · package.selflabbs.com
claude mcp add --transport http selflabbs-package-intel-mcp https://package.selflabbs.com/mcp
[mcp_servers.selflabbs-package-intel-mcp] url = "https://package.selflabbs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"selflabbs-package-intel-mcp": {
"type": "remote",
"url": "https://package.selflabbs.com/mcp",
"enabled": true
}
}
} openclaw mcp add selflabbs-package-intel-mcp --url https://package.selflabbs.com/mcp --transport streamable-http
mcp_servers:
selflabbs-package-intel-mcp:
url: "https://package.selflabbs.com/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://package.selflabbs.com/mcp
TLS unreached
DNSSEC inconclusive
Validation of package.selflabbs.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| package.selflabbs.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://package.selflabbs.com/mcp | Unreachable | ||
| http (plaintext) | http://package.selflabbs.com/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
package_dependencies ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | — |
| name | string | yes | — |
| version | string | — | Optional; defaults to the latest/default version |
No output schema declared.
No examples provided.
package_downloads ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | — |
| name | string | yes | — |
No output schema declared.
No examples provided.
package_health ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | — |
| name | string | yes | — |
No output schema declared.
No examples provided.
package_info ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | — |
| name | string | yes | Package/crate name |
No output schema declared.
No examples provided.
package_search ~57
Search for packages by keyword and get the top matches with descriptions. Supported ecosystems: npm and cargo (PyPI has no public search API).
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | — |
| limit | integer | — | — |
| query | string | yes | — |
No output schema declared.
No examples provided.
package_versions ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | — |
| limit | integer | — | — |
| name | string | yes | — |
No output schema declared.
No examples provided.