Lockstep
NPM · LOCKSTEP-CLI · SCANNED SEP 26
Decision memory for AI coding agents: captures decisions once, briefs every agent before it acts.
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
- 51 of 130 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability34
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 399 tokens (~21/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- 0% of tools have a non-trivial description (not blank, and not just the tool's name).Fail
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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 Lockstep MCP server?
Lockstep runs locally as an npm package, launched with npx -y lockstep-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · lockstep-cli
claude mcp add lockstep-team-agent-lockstep -- npx -y lockstep-cli
{
"mcpServers": {
"lockstep-team-agent-lockstep": {
"command": "npx",
"args": [
"-y",
"lockstep-cli"
]
}
}
} {
"servers": {
"lockstep-team-agent-lockstep": {
"command": "npx",
"args": [
"-y",
"lockstep-cli"
]
}
}
} codex mcp add lockstep-team-agent-lockstep -- npx -y lockstep-cli
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lockstep-team-agent-lockstep": {
"type": "local",
"command": [
"npx",
"-y",
"lockstep-cli"
],
"enabled": true
}
}
} openclaw mcp add lockstep-team-agent-lockstep --command npx --arg -y --arg lockstep-cli
mcp_servers:
lockstep-team-agent-lockstep:
command: "npx"
args: ["-y", "lockstep-cli"] {
"McpServers": {
"lockstep-team-agent-lockstep": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"lockstep-cli"
]
}
}
} assistant mcp add lockstep-team-agent-lockstep -t stdio -c npx -a -y lockstep-cli
{
"mcpServers": {
"lockstep-team-agent-lockstep": {
"command": "npx",
"args": [
"-y",
"lockstep-cli"
]
}
}
} 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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- 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 +3
- Stability: unverified → 0.20 ▲ functional
- Package version: 0.3.0 → 0.3.2 functional
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 +1
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 0 ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: poor functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- Package version: 0.2.0 → 0.3.0 functional
- 17 Sept 26 39
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 26 Sept 2026 · Analysed npm/lockstep-cli@0.3.2
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 130 packages
| Packages resolved | 130 |
|---|---|
| Deprecated | 1 |
| Stale | 50 |
| 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 →
ack_decision ~28
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| decisionId | string | yes | – |
| verdict | string | – | – |
| version | number | yes | – |
No output schema declared.
No examples provided.
ack_inbox ~14
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| itemIds | array | – | – |
No output schema declared.
No examples provided.
answer ~19
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| questionId | string | yes | – |
| response | string | yes | – |
No output schema declared.
No examples provided.
ask ~25
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| scope | string | – | – |
| urgent | boolean | – | – |
No output schema declared.
No examples provided.
check_decisions ~13
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | – |
No output schema declared.
No examples provided.
complete ~19
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| taskId | string | yes | – |
No output schema declared.
No examples provided.
consumers ~11
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| surface | string | yes | – |
No output schema declared.
No examples provided.
decisions ~11
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | – |
No output schema declared.
No examples provided.
delegate ~23
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| refs | – | – | – |
| task | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
get_product_context ~13
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | yes | – |
No output schema declared.
No examples provided.
inbox ~4
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
notify ~63
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilityRef | string | – | – |
| contractDelta | – | – | – |
| diffHash | string | – | – |
| riskTier | string | – | – |
| summary | string | yes | – |
| surface | string | – | – |
| verified | boolean | – | – |
| verifiedAgainst | string | – | – |
No output schema declared.
No examples provided.
propose_decision ~76
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | – |
| baseVersion | number | yes | – |
| capabilityRef | string | – | – |
| decisionType | string | – | – |
| rationale | string | – | – |
| reviewAt | string | – | – |
| ruleText | string | yes | – |
| scopeKind | string | yes | – |
| scopeRef | string | yes | – |
No output schema declared.
No examples provided.
query ~18
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| scope | string | – | – |
No output schema declared.
No examples provided.
refresh_decision_pack ~7
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_dependency ~22
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| producedRepoId | string | – | – |
| producedSurface | string | yes | – |
No output schema declared.
No examples provided.
session_briefing ~7
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_feature_context ~14
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilityRef | string | yes | – |
No output schema declared.
No examples provided.
whoowns ~12
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
What is the Lockstep MCP server?
Lockstep is an MCP server listed in the public MCP registry as io.github.lockstep-team-agent/lockstep. Decision memory for AI coding agents: captures decisions once, briefs every agent before it acts. This page covers its npm package (lockstep-cli).
Is the Lockstep MCP server safe to use?
Lockstep scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. 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 Lockstep MCP server expose?
Lockstep exposes 19 tools: notify, inbox, ack_inbox, query, ask, and 14 more. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.
Is the Lockstep MCP server still maintained?
Lockstep is still listed as active in the MCP registry. We last reached this channel on 26 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 Lockstep MCP server under?
Lockstep declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.