StackMap
NPM · @SHIP-WITH-AI/STACKMAP-MCP · SCANNED SEP 21
Search 344 human-reviewed AI/agent repos and the 817 typed connections between them.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Ship-With-AI/stackmap-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 370 tokens (~74/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 StackMap MCP server?
StackMap runs locally as an npm package, launched with npx -y @ship-with-ai/stackmap-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @ship-with-ai/stackmap-mcp
claude mcp add ship-with-ai-stackmap -- npx -y @ship-with-ai/stackmap-mcp
{
"mcpServers": {
"ship-with-ai-stackmap": {
"command": "npx",
"args": [
"-y",
"@ship-with-ai/stackmap-mcp"
]
}
}
} {
"servers": {
"ship-with-ai-stackmap": {
"command": "npx",
"args": [
"-y",
"@ship-with-ai/stackmap-mcp"
]
}
}
} codex mcp add ship-with-ai-stackmap -- npx -y @ship-with-ai/stackmap-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ship-with-ai-stackmap": {
"type": "local",
"command": [
"npx",
"-y",
"@ship-with-ai/stackmap-mcp"
],
"enabled": true
}
}
} openclaw mcp add ship-with-ai-stackmap --command npx --arg -y --arg @ship-with-ai/stackmap-mcp
mcp_servers:
ship-with-ai-stackmap:
command: "npx"
args: ["-y", "@ship-with-ai/stackmap-mcp"] {
"McpServers": {
"ship-with-ai-stackmap": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@ship-with-ai/stackmap-mcp"
]
}
}
} assistant mcp add ship-with-ai-stackmap -t stdio -c npx -a -y @ship-with-ai/stackmap-mcp
{
"mcpServers": {
"ship-with-ai-stackmap": {
"command": "npx",
"args": [
"-y",
"@ship-with-ai/stackmap-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 2 Sept 26 82
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 · Analysed npm/@ship-with-ai/stackmap-mcp@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Ship-With-AI/stackmap-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Ship-With-AI/stackmap-mcp/.github/workflows/publish.yml@refs/tags/v0.2.2 |
| Rekor log index | 2691207367 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:faa2145547fabe6db8459d677d81006de963552e387e0d5bbe3e2ee1d862d3906448eb3199c616a4ae2f03188d641d07af55ad3a52ac347af81af2dec |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
build_stack Build a stack from a description ~120
Describe what you are building; get a starter stack assembled from the curated map — seed repos matched to your description, expanded through human-reviewed "pairs well with" edges, every pick carrying the curator's written why. Deterministic composition over curated data (no LLM in this server) — treat it as a strong draft for your own judgment.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | what you are building, e.g. "a local-first RAG pipeline over PDFs with an agent frontend" |
| size | integer | – | target stack size (default 6) |
No output schema declared.
No examples provided.
continue_stack Continue your stack ~58
Given repos you already use, suggests what pairs well next — curated complements ranked by curator confidence, each with the written why.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | repo slugs already in your stack, e.g. ["langgraph","chroma"] |
No output schema declared.
No examples provided.
get_alternatives Alternatives to a repo ~42
Human-reviewed alternatives for a repo — same job, different tool — each with the written "when to pick which".
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | repo slug |
No output schema declared.
No examples provided.
get_repo Get one repo, fully mapped ~66
Full StackMap entry for a repo: summary, the opinionated curator note (including when NOT to use it), and every typed, human-reviewed relationship with its written why.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | repo slug, e.g. "langgraph" (try search_catalog if unsure) |
No output schema declared.
No examples provided.
search_catalog Search the StackMap catalog ~84
Search 200+ curated open-source AI/agent repos by keywords. Matches name, summary, curator note and topics. Returns ranked matches with the human-written "when to use it (and when not)".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max results (default 8) |
| query | string | yes | keywords, e.g. "local voice transcription" or "agent memory" |
No output schema declared.
No examples provided.
What is the StackMap MCP server?
StackMap is an MCP server listed in the public MCP registry as io.github.Ship-With-AI/stackmap. Search 344 human-reviewed AI/agent repos and the 817 typed connections between them. This page covers its npm package (@ship-with-ai/stackmap-mcp).
Is the StackMap MCP server safe to use?
StackMap scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 StackMap MCP server expose?
StackMap exposes 5 tools: search_catalog, get_repo, get_alternatives, continue_stack, build_stack. Their descriptions and schemas cost roughly 370 tokens of context every time the server is loaded.
Is the StackMap MCP server still maintained?
StackMap 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.
What licence is the StackMap MCP server under?
StackMap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.