storymapper

MCPcommunity
v1.0.1Thomas SchwengerApache-2.0Updated 2mo agonpmGitHub

User Story Map + Kanban board with a live HTTP/WebSocket UI and an MCP server, so AI agents and humans plan the same backlog together.

Works in
ClaudeCursorCopilotGemini

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
AuthorThomas Schwenger
LicenseApache-2.0
Version1.0.1
Sourcenpm+mcp-registry
npmstorymapper
GitHubTomAtAP/storymapper
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 31 resolved+ · none vulnerable
Tool surface40 tools · 5 privileged
Security scan✓ Cleanv1.0.1 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 20, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

40 tools · 5 privileged
Statically extracted from the published packagev1.0.1 · 1mo ago

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.

list_projectsNo description published

This tool published no description. Forge does not invent one.

project_getNo description published

This tool published no description. Forge does not invent one.

project_createNo description published

This tool published no description. Forge does not invent one.

project_updateNo description published

This tool published no description. Forge does not invent one.

project_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

list_ticketsNo description published

This tool published no description. Forge does not invent one.

next_actionableNo description published

This tool published no description. Forge does not invent one.

generate_product_docNo description published

This tool published no description. Forge does not invent one.

attachment_listNo description published

This tool published no description. Forge does not invent one.

attachment_putNo description published

This tool published no description. Forge does not invent one.

attachment_getNo description published

This tool published no description. Forge does not invent one.

attachment_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

ingest_slice_candidatesNo description published

This tool published no description. Forge does not invent one.

spec_module_createNo description published

This tool published no description. Forge does not invent one.

requirement_createNo description published

This tool published no description. Forge does not invent one.

requirement_listNo description published

This tool published no description. Forge does not invent one.

get_trace_coverageNo description published

This tool published no description. Forge does not invent one.

get_drift_reportNo description published

This tool published no description. Forge does not invent one.

query_ticketsNo description published

This tool published no description. Forge does not invent one.

ticket_getNo description published

This tool published no description. Forge does not invent one.

ticket_createNo description published

This tool published no description. Forge does not invent one.

ticket_updateNo description published

This tool published no description. Forge does not invent one.

ticket_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

change_ticket_statusNo description published

This tool published no description. Forge does not invent one.

cancel_ticketNo description published

This tool published no description. Forge does not invent one.

get_configNo description published

This tool published no description. Forge does not invent one.

set_configNo description published

This tool published no description. Forge does not invent one.

resolve_definitions_for_ticketNo description published

This tool published no description. Forge does not invent one.

set_checklist_itemNo description published

This tool published no description. Forge does not invent one.

mark_readyNo description published

This tool published no description. Forge does not invent one.

complete_ticketNo description published

This tool published no description. Forge does not invent one.

list_releasesNo description published

This tool published no description. Forge does not invent one.

release_createNo description published

This tool published no description. Forge does not invent one.

release_updateNo description published

This tool published no description. Forge does not invent one.

release_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

list_process_stepsNo description published

This tool published no description. Forge does not invent one.

process_step_createNo description published

This tool published no description. Forge does not invent one.

process_step_updateNo description published

This tool published no description. Forge does not invent one.

process_step_deleteprivilegedNo description published

This tool published no description. Forge does not invent one.

split_process_stepNo description published

This tool published no description. Forge does not invent one.

0 of 40 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.

About

User Story Map + Kanban board with a live HTTP/WebSocket UI and an MCP server, so AI agents and humans plan the same backlog together.

Keywords
story-mapuser-story-mapkanbanagilebacklogmcpmodel-context-protocolclaudeai-agentsqliteproject-planning
Alternatives
Comparing tool surfaces…

Tools exposed

40 tools · 5 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in databases