Skip to main content
Glama

xyz MCP by CyberXYZ

Server Details

Package verdicts for AI coding agents: check npm, PyPI, Go and NuGet installs before they run.

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

A3.9/5.0

Scored across 5 tools

Disambiguation4/5

Most tools have clearly distinct targets: search finds packages, get_vulnerability elaborates an advisory id, and model_risk covers Hugging Face models. The main boundary risk is check_package vs package_info, which both return package safety reports, but the descriptions explicitly distinguish version-level verdicts from package-level reports, so an agent can choose correctly with care.

Naming Consistency3/5

The set mixes conventions: verb_noun (check_package, get_vulnerability), bare verb (search), and noun phrases (model_risk, package_info). Names are individually readable, but there is no single predictable pattern an agent can rely on to infer a name.

Tool Count5/5

Five tools is well within a healthy range and each maps to a distinct workflow step: discover (search), inspect (package_info), decide (check_package), explain (get_vulnerability), and assess models (model_risk). Nothing appears redundant or bolted on.

Completeness4/5

Core lifecycle is covered: discovery, package-level details, version-level install verdicts, advisory drill-down, and model risk. Gaps are less about missing operations than scale—no bulk/manifest or lockfile checking, no way to list advisories by ecosystem or recency—which agents can approximate with repeated calls.

Available Tools

5 tools
check_packageA
Read-only
Inspect

Public safety verdict for ONE package (optionally one version) from CyberXYZ's global threat data: known-malicious releases (always shown in full), advisories, commit-level analysis and version anomalies. Call it BEFORE adding or installing an npm, PyPI, Go or NuGet dependency. decision: block or quarantine = do not install; alert = installable but flagged; allow = ok; unknown = no record, not vetted: ask the user; unverified = the check did not complete: retry, then ask the user. Signing in adds the full install-time verdict (see sign_in_adds).

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

get_vulnerabilityA
Read-only
Inspect

Full detail for one advisory id (CVE-..., GHSA-..., or an OSV id such as PYSEC-...): every affected package (affected_packages: package, ecosystem, ranges, fixed), the primary one's version ranges and fixed version, severity, CVSS, EPSS (probability of exploitation in 30 days), CISA KEV (exploited in the wild), references and how many packages depend on the affected one. Pass package / ecosystem to describe a specific affected package. Use it to explain an advisory to the user.

Inputs: id (required), package, ecosystem.

model_riskA
Read-only
Inspect

CyberXYZ's public report on a Hugging Face model's install risk: risk level, XYZ score, the driving reason, the worst dependencies and recent risk events. verdict UNKNOWN (not watched, pending, gated) is not safe: ask the user. Signing in adds every reason, all flagged dependencies and per-file load safety.

Inputs: repo_id (required).

package_infoA
Read-only
Inspect

CyberXYZ's public report for a package: every published advisory (CVE/GHSA ids, severity, CVSS, EPSS, KEV, affected ranges, fixed version), malicious-package records in full, how many packages depend on it, what it pulls in (counts and worst severity) and AI-model usage. Package-level; for a verdict on a specific version call check_package.

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

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
      B
      maintenance
      Enables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.
      3
      52 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to check package names and versions for allow/warn/deny verdicts, scan project lockfiles for known-malicious packages and critical advisories, and suggest safe versions across npm, PyPI, crates.io, and Go before manifests are edited.
      36 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      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
    • 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
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources