# @ship-with-ai/stackmap-mcp

MCP server for StackMap — the curated map of the open-source AI stack. Search 344 human-reviewed repos across 21 topics, 817 typed relationships (complements / alternative / built_with), and the written why behind every connection.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.2.2
- **Author:** ShipWithAI
- **License:** MIT
- **npm:** @ship-with-ai/stackmap-mcp
- **Source:** https://github.com/Ship-With-AI/stackmap-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-05T18:15:33.234Z
- **Version scanned:** 0.2.2
- **CVEs:** none found by OSV at scan time

## Tools

5 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `search_catalog` — 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 
- `get_repo` — 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 writ
- `get_alternatives` — Human-reviewed alternatives for a repo — same job, different tool — each with the written "when to pick which".
- `continue_stack` — Given repos you already use, suggests what pairs well next — curated complements ranked by curator confidence, each with the written why.
- `build_stack` — Describe what you are building; get a starter stack assembled from the curated map — seed repos matched to your description, expanded through human-reviewed "pa

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"stackmap\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@ship-with-ai/stackmap-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40ship-with-ai%2Fstackmap-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40ship-with-ai%2Fstackmap-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40ship-with-ai%2Fstackmap-mcp
- HTML page: https://forgeregistry.com/registry/%40ship-with-ai%2Fstackmap-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.