MCP serverio.github.IsaiahDupree/devstack-mcp
Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.
Overview
Score?
UNRATED 0.784
of what a free look can see, on 30 looks
Looks
35
last 17 hr ago
Tools
10
More info
URL
devstack-mcp.vercel.app/mcp
streamable-http
Says it is
devstack 1.0.0
protocol 2025-06-18
In the record since
32 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.784 · highest on record 0.8561
Toolsfrom sha256:21645ff934…dce4ad
| Tool | Schema |
|---|---|
| get_dependency_graph The fully resolved dependency graph for one exact package version, via deps.dev. Returns a flat nodes[] array plus integer-index edges[] (walk from/to to rebuild the tree). Each no |
input · no output |
| get_downloads Download statistics for a package. Only npm (via api.npmjs.org) and PyPI (via pypistats.org) support this; any other registry returns 400 not_supported. npm returns a period window |
input · no output |
| get_ecosystems_package Full normalized metadata for one package on one of 50+ registries, via ecosyste.ms — including the fields v1 registries can't give you: dependentReposCount and dependentPackagesCou |
input · no output |
| get_insights Health and security insights for a package's source project, via deps.dev. Returns the linked source repository, GitHub stars/forks/openIssues, licenses, resolved dependencyCount, |
input · no output |
| get_package Full normalized details for one package by registry + name, in a single unified Package shape across npm, PyPI, Docker Hub, and the VS Code Marketplace. name handles scoped npm ids |
input · no output |
| get_versions List published versions (npm/PyPI), image tags (Docker Hub, most recent 25), or extension versions (VS Code) for a package. registry=all is NOT supported here — pick a single regis |
input · no output |
| get_vulnerabilities Known vulnerabilities (CVE / GHSA / PYSEC / GO advisories) for a package, via OSV.dev. Pass version to filter to advisories affecting that exact version, or omit it for the package |
input · no output |
| scan_vulnerabilities_batch Scan many packages in one call — ideal for a whole lockfile. Pass a queries[] array (max 100) of { ecosystem, name, version? }; results are returned positionally aligned, one row p |
input · no output |
| search_ecosystems Look a package name up across 50+ registries at once, via ecosyste.ms. This is an EXACT-name lookup (not fuzzy full-text): q=react returns the react package everywhere it exists (n |
input · no output |
| search_packages Search a registry for packages matching q. registry=all fans out to npm, Docker Hub, and the VS Code Marketplace and merges the results. PyPI has no public search API, so registry= |
input · no output |
Verify it yourself
npx teppi-check https://devstack-mcp.vercel.app/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2CQKYJBQK0B6BET3GV4N