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.

io.github.yashdoke7/skeletongraph

PYPI · SKELETONGRAPH

Zero-LLM structural code retrieval for AI coding agents, served over MCP.

Available components

0 this week 0 Trust /100

Last scanned (10 minutes ago)

Scores higher than 0% of PyPI servers

Category Code Search and Documentation

Recent critical change

GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security75
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

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.

  • 22 Oct 26 0
    • GHSA-6q48-6c7w-9gw2 no longer affects this package ▲ security
  • 21 Oct 26 0
    • GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
  • 18 Oct 26 0
    • Dependency health: partial → 0.99 functional
  • 17 Oct 26 0
    • Dependency health: 0.99 → partial functional
  • 13 Oct 26 0
    • Malware scan: unverified → pass ▲ security
    • Dependency health: partial → 0.99 functional
  • 12 Oct 26 0
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.99 → partial functional
  • 2 Oct 26 0
    • Malware scan: unverified → pass ▲ security
  • 1 Oct 26 −32
    • CVE-2026-68770 affects this package: high ▼ critical
    • Score status: scored → failed ▼ critical
    • Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
    • Malware scan: pass → unverified ▼ security
    • CVE-2026-5241 no longer affects this package ▲ security
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 5 Nov 2026 · Analysed pypi/skeletongraph@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 13 findings
ID CVE Severity Vector Fix available
GHSA-jhr6-gm9c-rqjv CVE-2026-68770 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
PYSEC-2026-4164 CVE-2026-68770 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-29pf-2h5f-8g72 CVE-2026-4372 high CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yes
GHSA-69w3-r845-3855 CVE-2026-1839 medium CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:H yes
GHSA-fgcw-684q-jj6r CVE-2026-5241 high CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N yes
GHSA-x9r9-c232-4q39 CVE-2026-80047 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
GHSA-xrqw-3rrv-vx5w CVE-2026-9856 high CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L yes
PYSEC-2025-217 CVE-2025-14929 high CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H no
PYSEC-2026-2288 CVE-2026-1839 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2289 CVE-2026-4372 high CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2290 CVE-2026-5241 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H no
PYSEC-2026-3929 CVE-2026-9856 high CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L yes
PYSEC-2026-4174 CVE-2026-80047 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no

Background: What a vulnerability scan can and cannot prove →

Dependencies 78 packages
Packages resolved 78
Stale 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.yashdoke7/skeletongraph MCP server?

io.github.yashdoke7/skeletongraph runs locally as a PyPI package, launched with uvx skeletongraph. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · skeletongraph

# add to Claude Code
claude mcp add yashdoke7-skeletongraph -- uvx skeletongraph
Common questions

What is the io.github.yashdoke7/skeletongraph MCP server?

io.github.yashdoke7/skeletongraph is an MCP server listed in the public MCP registry as io.github.yashdoke7/skeletongraph. Zero-LLM structural code retrieval for AI coding agents, served over MCP. This page covers its PyPI package (skeletongraph).

Is the io.github.yashdoke7/skeletongraph MCP server still maintained?

io.github.yashdoke7/skeletongraph is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.yashdoke7/skeletongraph MCP server under?

io.github.yashdoke7/skeletongraph declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.