Compose MCP
NPM · @SMARTMEMORY/COMPOSE-MCP · SCANNED SEP 27
Typed feature management for compose projects: roadmap, changelog, artifacts, journal.
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 Security88
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 400 of 585 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 585 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
- Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the Compose MCP server?
Compose MCP runs locally as an npm package, launched with npx -y @smartmemory/compose-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 · @smartmemory/compose-mcp
claude mcp add ai-smartmemory-compose-mcp -- npx -y @smartmemory/compose-mcp
{
"mcpServers": {
"ai-smartmemory-compose-mcp": {
"command": "npx",
"args": [
"-y",
"@smartmemory/compose-mcp"
]
}
}
} {
"servers": {
"ai-smartmemory-compose-mcp": {
"command": "npx",
"args": [
"-y",
"@smartmemory/compose-mcp"
]
}
}
} codex mcp add ai-smartmemory-compose-mcp -- npx -y @smartmemory/compose-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-smartmemory-compose-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@smartmemory/compose-mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-smartmemory-compose-mcp --command npx --arg -y --arg @smartmemory/compose-mcp
mcp_servers:
ai-smartmemory-compose-mcp:
command: "npx"
args: ["-y", "@smartmemory/compose-mcp"] {
"McpServers": {
"ai-smartmemory-compose-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@smartmemory/compose-mcp"
]
}
}
} assistant mcp add ai-smartmemory-compose-mcp -t stdio -c npx -a -y @smartmemory/compose-mcp
{
"mcpServers": {
"ai-smartmemory-compose-mcp": {
"command": "npx",
"args": [
"-y",
"@smartmemory/compose-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.
- 27 Sept 26 −29
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Package version: 0.7.0 → 0.7.1 functional
- 26 Sept 26 +37
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.6.5 → 0.7.0 functional
- 25 Sept 26 −31
- Known CVEs: partial → unverified ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- License: pass → fail ▼ functional
- First check of Schema quality: unverified functional
- Licence: MIT → BUSL-1.1 functional
- Package version: 0.6.3 → 0.6.5 functional
- Package version: 0.6.3 → 0.6.4 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.57 → fail ▼ security
- Package version: 0.4.1 → 0.6.3 functional
- 22 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 27 Sept 2026 · Analysed npm/@smartmemory/compose-mcp@0.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Stale | 159 |
| No linked repository | 18 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
write_journal_entry ~216
Write a typed entry to compose/docs/journal/ with auto-numbered global session and inserted index row. Idempotent on (date, slug) at storage level; optional caller idempotency_key for retry safety. Audit-log append is best-effort.
| Name | Type | Req | Description |
|---|---|---|---|
| closing_line | string | – | Optional final italicized one-liner. |
| date | string | yes | ISO date "YYYY-MM-DD". |
| feature_code | string | – | Optional feature code stamped in entry frontmatter. |
| force | boolean | – | If true and an entry with the same (date, slug) exists, overwrite in place. |
| idempotency_key | string | – | Optional caller-supplied key. Same key replays return the cached result without re-mutating. |
| sections | object | yes | – |
| slug | string | yes | Kebab-case slug for the filename, e.g. "mcp-journal-writer". |
| summary_for_index | string | yes | Single-line summary for the README index row. No newlines, no "|". |
No output schema declared.
No examples provided.
What is the Compose MCP server?
Compose MCP is listed in the public MCP registry as ai.smartmemory/compose-mcp. Typed feature management for compose projects: roadmap, changelog, artifacts, journal. This page covers its npm package (@smartmemory/compose-mcp).
Is the Compose MCP server safe to use?
Compose MCP scores 28 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 Compose MCP server expose?
Compose MCP exposes 51 tools: get_vision_items, get_item_detail, get_phase_summary, get_blocked_items, get_current_session, and 46 more. Their descriptions and schemas cost roughly 7,225 tokens of context every time the server is loaded.
Is the Compose MCP server still maintained?
Compose MCP is still listed as active in the MCP registry. We last reached this channel on 27 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 Compose MCP server under?
Compose MCP declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.