# devstack-mcp MCP server

Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-isaiahdupree-devstack-mcp
- Repository: https://github.com/IsaiahDupree/devstack-mcp
- Website: https://devstack-mcp.vercel.app

## Install
- Endpoint: https://devstack-mcp.vercel.app/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://devstack-mcp.vercel.app/mcp

## Tools
- get_package (Get normalized package details) - 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 (e.g. @types/node), Docker namespaces (e.g. library/nginx or a bare nginx for official images), and VS Code publisher.extension ids. With registry=all the request fans out to every registry in parallel and returns a packages array (missing registries are silently dropped); otherwise a single package is returned. Endpoint: https://devstack-mcp.vercel.app/mcp
- search_packages (Search packages across registries) - 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=pypi returns 400 not_supported — look a PyPI package up by name via get_package instead. Results are normalized PackageSummary items (npm adds a relevance score; Docker adds isOfficial). Endpoint: https://devstack-mcp.vercel.app/mcp
- get_versions (Get published versions / tags) - 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 registry. Each item carries version and released, plus registry-specific extras (files for PyPI, size for Docker tags). Endpoint: https://devstack-mcp.vercel.app/mcp
- get_downloads (Get download / pull statistics) - 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 with downloads, start, and end; PyPI returns last_day, last_week, and last_month totals. Endpoint: https://devstack-mcp.vercel.app/mcp
- get_dependency_graph (Get resolved 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 node carries relation (self | direct | indirect) and a direct boolean; node[0] is always the queried root (relation: self). Node order is NOT stable — look nodes up by name/relation, never by positional index. system is case-insensitive and lowercased (npm, pypi, cargo, go, maven, nuget). version is REQUIRED (a graph is resolved for one exact version). Endpoint: https://devstack-mcp.vercel.app/mcp
- get_vulnerabilities (Get vulnerabilities for a package) - 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's full advisory history. Each result carries the OSV id, cross-id aliases, a severity word grade (LOW|MODERATE|HIGH|CRITICAL), the cvss vector string, affectedRanges with fixed-version events, references, and cwes. A clean package returns count: 0 with an empty list (not an error). ecosystem is CASE-SENSITIVE — use OSV's spelling (npm, PyPI, Go, crates.io, Maven, NuGet, RubyGems, …). Use scan_vulnerabilities_batch for lockfile batch scans. Endpoint: https://devstack-mcp.vercel.app/mcp
- scan_vulnerabilities_batch (Batch vulnerability scan (lockfile)) - 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 per query, each with a count and a hydrated vulns[] array. Advisories are de-duplicated and hydrated across the batch. ecosystem is CASE-SENSITIVE (OSV spelling). Endpoint: https://devstack-mcp.vercel.app/mcp
- get_insights (Get project insights — OSSF Scorecard + repo signal) - 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, security advisories, and the full OSSF Scorecard (ossfScore 0..10 plus the per-check breakdown). Omit version to use the registry default version — note deps.dev's default is a MOVING target and an unverified default mirror may have no computed scorecard (ossfScore: null); pin version for a stable, scorecard-backed result. system is lowercased (npm, pypi, cargo, go, maven, …). Endpoint: https://devstack-mcp.vercel.app/mcp
- search_ecosystems (Cross-registry package lookup (50+ 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 (npm, cargo, nuget, pub, bower, …), each as a normalized ecosystemsPackage with reverse-dependency counts. Pass ecosystem to narrow to one registry. Results carry dependentReposCount, dependentPackagesCount, and vulnerabilityCount. Endpoint: https://devstack-mcp.vercel.app/mcp
- get_ecosystems_package (Get one package on one registry (with reverse-dep counts)) - 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 dependentPackagesCount (reverse dependencies), ecosystem, and vulnerabilityCount. Scoped/namespaced names are handled automatically. Returns 404 if the package does not exist on that ecosystem. Endpoint: https://devstack-mcp.vercel.app/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.IsaiahDupree
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Aug 1, 2026
- Source: https://registry.modelcontextprotocol.io