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.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
search_catalogSearch 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)".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)".
No input schema was published for this tool.
get_repoFull 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.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.
No input schema was published for this tool.
get_alternativesHuman-reviewed alternatives for a repo — same job, different tool — each with the written "when to pick which".Human-reviewed alternatives for a repo — same job, different tool — each with the written "when to pick which".
No input schema was published for this tool.
continue_stackGiven repos you already use, suggests what pairs well next — curated complements ranked by curator confidence, each with the written why.Given repos you already use, suggests what pairs well next — curated complements ranked by curator confidence, each with the written why.
No input schema was published for this tool.
build_stackDescribe 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) —…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) —…
No input schema was published for this tool.
5 of 5 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
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.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.