Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

pkg-oracle — Dependency Trust Oracle

REMOTE · MCP-SNOWY-DEW-9447.FLY.DEV · SCANNED AUG 7

Pay-per-call dependency trust oracle: verifies npm/PyPI packages before an AI agent installs them.

63 Trust /100
Trust breakdown (6 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

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 · mcp-snowy-dew-9447.fly.dev

# add to Claude Code
claude mcp add --transport http julian-martin89-pkg-oracle https://mcp-snowy-dew-9447.fly.dev/mcp
# ~/.codex/config.toml
[mcp_servers.julian-martin89-pkg-oracle]
url = "https://mcp-snowy-dew-9447.fly.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "julian-martin89-pkg-oracle": {
      "type": "remote",
      "url": "https://mcp-snowy-dew-9447.fly.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add julian-martin89-pkg-oracle --url https://mcp-snowy-dew-9447.fly.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  julian-martin89-pkg-oracle:
    url: "https://mcp-snowy-dew-9447.fly.dev/mcp"
// mcp.json
{
  "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.

Changelog

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.

  • 6 Aug 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.

  • 5 Aug 26 +24
    • 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
    • Stability: unverified → 0.03 functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • New tool “verify_package” functional
  • 4 Aug 26 38

    First indexed and scored.

Diagnostics

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 7 Aug 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=YE2,O=Let's Encrypt,C=US 21 Jun 2026 19 Sept 2026 ECDSA 256 ECDSA-SHA384 503153e73302e4a0c89ebb83c4a741aac04
SANs: *.fly.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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
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
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
MCP tools · 1 exposed · ~281 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
ecosystemstringyesPackage registry to check the name against.
namestringyesExact package name as it would appear in the manifest (case-sensitive for npm scoped packages).
versionstringOptional exact version string to verify (e.g. "4.17.21"). Omit to check only the package name.

No output schema declared.

No examples provided.