pkg-oracle — Dependency Trust Oracle
REMOTE · MCP-SNOWY-DEW-9447.FLY.DEV · SCANNED SEP 24
Blocks typosquatted or hallucinated npm/PyPI packages before an AI agent installs them.
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 → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 281 tokens (~281/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the pkg-oracle — Dependency Trust Oracle MCP server?
pkg-oracle — Dependency Trust Oracle is a hosted endpoint at https://mcp-snowy-dew-9447.fly.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.
remote · mcp-snowy-dew-9447.fly.dev
claude mcp add --transport http julian-martin89-pkg-oracle 'https://mcp-snowy-dew-9447.fly.dev/mcp'
{
"mcpServers": {
"julian-martin89-pkg-oracle": {
"url": "https://mcp-snowy-dew-9447.fly.dev/mcp"
}
}
} {
"servers": {
"julian-martin89-pkg-oracle": {
"type": "http",
"url": "https://mcp-snowy-dew-9447.fly.dev/mcp"
}
}
} [mcp_servers.julian-martin89-pkg-oracle] url = "https://mcp-snowy-dew-9447.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"julian-martin89-pkg-oracle": {
"type": "remote",
"url": "https://mcp-snowy-dew-9447.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add julian-martin89-pkg-oracle --url 'https://mcp-snowy-dew-9447.fly.dev/mcp' --transport streamable-http
mcp_servers:
julian-martin89-pkg-oracle:
url: "https://mcp-snowy-dew-9447.fly.dev/mcp" {
"McpServers": {
"julian-martin89-pkg-oracle": {
"Transport": "http",
"Url": "https://mcp-snowy-dew-9447.fly.dev/mcp"
}
}
} assistant mcp add julian-martin89-pkg-oracle -t streamable-http -u 'https://mcp-snowy-dew-9447.fly.dev/mcp'
{
"mcpServers": {
"julian-martin89-pkg-oracle": {
"type": "http",
"url": "https://mcp-snowy-dew-9447.fly.dev/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.
- 3 Sept 26 +1
- Stability: 0.97 → pass security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +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.
- 26 Aug 26 75
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 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
- 5 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Tool coverage: 100 functional
- New tool “verify_package” functional
- 4 Aug 26 0
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 24 Sept 2026 · Probed https://mcp-snowy-dew-9447.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-snowy-dew-9447.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-snowy-dew-9447.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-snowy-dew-9447.fly.dev/mcp | HTTPS enforced | 301 | https://mcp-snowy-dew-9447.fly.dev/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
verify_package Verify Package ~281
Dependency Trust Oracle. Call this BEFORE writing any package into a manifest (package.json, requirements.txt, pyproject.toml, ...). It checks whether the package actually exists on its registry, cross-references OSV.dev for known CVEs, pulls the package's OpenSSF Scorecard via deps.dev, and runs a Levenshtein-distance typosquat/slopsquat check against a curated list of popular packages combined with the package's publish age. Returns a synthetic verdict: ALLOW (no issues found), WARN (proceed with caution — read the findings before installing), or BLOCK (do not install — likely a hallucinated package name, an active typosquat, or a known critical/high-severity vulnerability). Always call this before running an install command for a package you have not already verified in this session. First 5 calls per caller are free; after that this tool requires x402 payment (USDC on Base) and will return a payment-required error with the amount and address to pay.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package registry to check the name against. |
| name | string | yes | Exact package name as it would appear in the manifest (case-sensitive for npm scoped packages). |
| version | string | – | Optional exact version string to verify (e.g. "4.17.21"). Omit to check only the package name. |
No output schema declared.
No examples provided.
What is the pkg-oracle — Dependency Trust Oracle MCP server?
pkg-oracle — Dependency Trust Oracle is an MCP server listed in the public MCP registry as io.github.julian-martin89/pkg-oracle. Blocks typosquatted or hallucinated npm/PyPI packages before an AI agent installs them. This page covers its hosted endpoint (https://mcp-snowy-dew-9447.fly.dev/mcp).
Is the pkg-oracle — Dependency Trust Oracle MCP server safe to use?
pkg-oracle — Dependency Trust Oracle scores 79 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 pkg-oracle — Dependency Trust Oracle MCP server expose?
pkg-oracle — Dependency Trust Oracle exposes 1 tool: verify_package. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.
Does the pkg-oracle — Dependency Trust Oracle MCP server require authentication?
No. We connected to pkg-oracle — Dependency Trust Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the pkg-oracle — Dependency Trust Oracle MCP server still maintained?
pkg-oracle — Dependency Trust Oracle is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.