io.github.IsaiahDupree/devstack-mcp
REMOTE · DEVSTACK-MCP.VERCEL.APP · SCANNED SEP 21
Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1566 tokens (~156/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.IsaiahDupree/devstack-mcp server?
io.github.IsaiahDupree/devstack-mcp is a hosted endpoint at https://devstack-mcp.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · devstack-mcp.vercel.app
claude mcp add --transport http isaiahdupree-devstack-mcp 'https://devstack-mcp.vercel.app/mcp'
{
"mcpServers": {
"isaiahdupree-devstack-mcp": {
"url": "https://devstack-mcp.vercel.app/mcp"
}
}
} {
"servers": {
"isaiahdupree-devstack-mcp": {
"type": "http",
"url": "https://devstack-mcp.vercel.app/mcp"
}
}
} [mcp_servers.isaiahdupree-devstack-mcp] url = "https://devstack-mcp.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"isaiahdupree-devstack-mcp": {
"type": "remote",
"url": "https://devstack-mcp.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add isaiahdupree-devstack-mcp --url 'https://devstack-mcp.vercel.app/mcp' --transport streamable-http
mcp_servers:
isaiahdupree-devstack-mcp:
url: "https://devstack-mcp.vercel.app/mcp" {
"McpServers": {
"isaiahdupree-devstack-mcp": {
"Transport": "http",
"Url": "https://devstack-mcp.vercel.app/mcp"
}
}
} assistant mcp add isaiahdupree-devstack-mcp -t streamable-http -u 'https://devstack-mcp.vercel.app/mcp'
{
"mcpServers": {
"isaiahdupree-devstack-mcp": {
"type": "http",
"url": "https://devstack-mcp.vercel.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 31 Aug 26 +1
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Aug 26 0
First indexed and scored.
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 21 Sept 2026 · Probed https://devstack-mcp.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of devstack-mcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://devstack-mcp.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://devstack-mcp.vercel.app/mcp | HTTPS enforced | 308 | https://devstack-mcp.vercel.app/mcp |
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 →
get_dependency_graph Get resolved dependency graph ~190
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).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name / id. |
| system | string | yes | Package system / ecosystem for deps.dev. Case-insensitive, lowercased server-side. |
| version | string | yes | Exact version to resolve (e.g. 18.2.0). Required. |
No output schema declared.
No examples provided.
get_downloads Get download / pull statistics ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name. |
| registry | string | yes | Target registry. Only npm and pypi expose download stats. |
No output schema declared.
No examples provided.
get_ecosystems_package Get one package on one registry (with reverse-dep counts) ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Target ecosyste.ms ecosystem slug (e.g. npm, pypi, cargo, rubygems). |
| name | string | yes | Package name / id. |
No output schema declared.
No examples provided.
get_insights Get project insights — OSSF Scorecard + repo signal ~195
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, …).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name / id. |
| system | string | yes | Package system / ecosystem for deps.dev. Case-insensitive, lowercased server-side. |
| version | string | – | Exact version. Omit for the (moving) registry default version. |
No output schema declared.
No examples provided.
get_package Get normalized package details ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name / id. Supports scoped npm ids (@scope/pkg), Docker namespaces (ns/name or a bare name for official images), and VS Code publisher.extension ids. |
| registry | string | yes | Target registry. "all" fans out to every registry and merges results. |
No output schema declared.
No examples provided.
get_versions Get published versions / tags ~121
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).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Package name / id (scoped npm ids, Docker namespaces, and VS Code publisher.extension ids supported). |
| registry | string | yes | Target registry. "all" is not supported here — pick one. |
No output schema declared.
No examples provided.
get_vulnerabilities Get vulnerabilities for a package ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | OSV ecosystem, CASE-SENSITIVE (e.g. npm, PyPI, Go, crates.io, Maven, NuGet, RubyGems). |
| name | string | yes | Package name. |
| version | string | – | Exact version to filter advisories to. Omit for full history. |
No output schema declared.
No examples provided.
scan_vulnerabilities_batch Batch vulnerability scan (lockfile) ~118
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).
| Name | Type | Req | Description |
|---|---|---|---|
| queries | array | yes | Up to 100 { ecosystem, name, version? } queries, ideal for a whole lockfile. |
No output schema declared.
No examples provided.
search_ecosystems Cross-registry package lookup (50+ ecosystems) ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Narrow to one ecosystem (e.g. pypi, npm, cargo). Omit to search all. |
| limit | integer | – | Max results. Clamped to 1-50. Default 20. |
| q | string | yes | Exact package name to look up across registries. |
No output schema declared.
No examples provided.
search_packages Search packages across registries ~152
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per registry. Clamped to 1-50. Default 20. |
| q | string | yes | Search query. |
| registry | string | yes | Target registry. "all" fans out to npm, Docker, and VS Code and merges results. pypi returns not_supported. |
No output schema declared.
No examples provided.
What is the io.github.IsaiahDupree/devstack-mcp server?
io.github.IsaiahDupree/devstack-mcp is listed in the public MCP registry as io.github.IsaiahDupree/devstack-mcp. Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems. This page covers its hosted endpoint (https://devstack-mcp.vercel.app/mcp).
Is the io.github.IsaiahDupree/devstack-mcp server safe to use?
io.github.IsaiahDupree/devstack-mcp scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.IsaiahDupree/devstack-mcp server expose?
io.github.IsaiahDupree/devstack-mcp exposes 10 tools: get_package, search_packages, get_versions, get_downloads, get_dependency_graph, and 5 more. Their descriptions and schemas cost roughly 1,566 tokens of context every time the server is loaded.
Does the io.github.IsaiahDupree/devstack-mcp server require authentication?
No. We connected to io.github.IsaiahDupree/devstack-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.IsaiahDupree/devstack-mcp server still maintained?
io.github.IsaiahDupree/devstack-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.