Skip to main content
Glama

pkg-oracle — Dependency Trust Oracle

Server Details

Blocks typosquatted or hallucinated npm/PyPI packages before an AI agent installs them.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of misselection or overlapping purpose. Its scope (verify a package's existence, CVEs, scorecard, and typosquat risk) is clearly stated and self-contained.

Naming Consistency5/5

verify_package follows a clean verb_noun snake_case convention. With a single tool there is no mixed convention to create inconsistency, and the name matches the described action exactly.

Tool Count4/5

A single-tool surface is defensible for a narrowly scoped trust oracle that performs one composite check, but it sits below the typical 3-15 sweet spot and offers no alternate entry points. Nothing is redundant, so the count is lean rather than incoherent.

Completeness3/5

The core check (existence, OSV CVEs, OpenSSF Scorecard, typosquat detection) is thorough for one package, but obvious adjacent operations are missing: batch/manifest-wide verification, re-verification or cache status within a session, and any way to inspect the trust database the tool consults. Agents verifying a full dependency file must loop one call per package, which is a notable gap.

Available Tools

1 tool
verify_packageVerify PackageAInspect

Dependency Trust Oracle. Call this BEFORE writing any package into a manifest (package.json, requirements.txt, pyproject.toml, Cargo.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.

Inputs: name (required), ecosystem (required), version.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Verifies npm package names for safety, detecting typosquats and nonexistent packages before your coding agent installs them.
      2
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Validates and checks packages across 19 ecosystems to prevent AI agents from installing hallucinated, deprecated, or malicious packages.
      60 npm
      AGPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Pre-install gate for AI coding agents. Checks npm, PyPI and crates.io package names before an install runs and blocks names that do not exist, were registered after models invented them, or sit one keystroke from a popular package. CLI, GitHub Action and MCP server. Apache 2.0.
      1
      306 PyPI
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to automatically verify npm packages against the live registry before installation, flagging hallucinated, slopsquatted, or otherwise suspicious packages with risk verdicts.
      4 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources