Stepgate
NPM · STEPGATE · SCANNED OCT 2
Agents can't skip steps: runs gated stepfiles on the client's own model.
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
- 32 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Chaarangan/stepgate). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 730 tokens (~91/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Stepgate MCP server?
Stepgate runs locally as an npm package, launched with npx -y stepgate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · stepgate
claude mcp add chaarangan-stepgate -- npx -y stepgate
{
"mcpServers": {
"chaarangan-stepgate": {
"command": "npx",
"args": [
"-y",
"stepgate"
]
}
}
} {
"servers": {
"chaarangan-stepgate": {
"command": "npx",
"args": [
"-y",
"stepgate"
]
}
}
} codex mcp add chaarangan-stepgate -- npx -y stepgate
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chaarangan-stepgate": {
"type": "local",
"command": [
"npx",
"-y",
"stepgate"
],
"enabled": true
}
}
} openclaw mcp add chaarangan-stepgate --command npx --arg -y --arg stepgate
mcp_servers:
chaarangan-stepgate:
command: "npx"
args: ["-y", "stepgate"] {
"McpServers": {
"chaarangan-stepgate": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"stepgate"
]
}
}
} assistant mcp add chaarangan-stepgate -t stdio -c npx -a -y stepgate
{
"mcpServers": {
"chaarangan-stepgate": {
"command": "npx",
"args": [
"-y",
"stepgate"
]
}
}
} 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.
- 29 Sept 26 +10
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.84 ▲ functional
- 28 Sept 26 71
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 2 Oct 2026 · Analysed npm/stepgate@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Chaarangan/stepgate |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Chaarangan/stepgate/.github/workflows/release.yml@refs/tags/v0.1.4 |
| Rekor log index | 2981242470 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6946ffa48b72ab792b3628a1d725d45e2e1818ac06a22029c607799f74533251d197e1cd477bf035cd8527062b9527dfa5d95a88bd25a9229458ea839 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 32 |
| 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 →
stepgate_call Call a step operation ~80
Calls one of the current step's operations for a Stepgate run and returns its result. Stepgate makes the request and adds any credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Arguments matching the operation's schema. |
| operation | string | yes | An operation the current step lists. |
| run | string | yes | The run id a stepfile tool returned. |
No output schema declared.
No examples provided.
stepgate_examples Catalog stepfiles to learn from ~55
Lists the catalog's stepfiles, or with a name returns that stepfile's YAML and README, to copy a working pattern from.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | A catalog stepfile's id; omit it for the list. |
No output schema declared.
No examples provided.
stepgate_guide How to write a stepfile ~42
Returns how to write a stepfile: the authoring workflow, the full format reference and the JSON Schema. Call it before writing or editing a stepfile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stepgate_inspect_api Inspect an API for a stepfile ~123
Fetches a public OpenAPI document or MCP server without credentials and reports what a stepfile needs: the document's sha256, servers, security schemes and operationIds, or an MCP server's tools and their schema_sha256.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| operations | array | – | Return the full argument schema of these operationIds or tool names. |
| search | string | – | Only list operations or tools whose name, path or description contains this. |
| url | string | yes | The OpenAPI document's URL, or the MCP server's endpoint. |
No output schema declared.
No examples provided.
stepgate_outline Outline a stepfile from a procedure ~83
Turns a SKILL.md or markdown SOP into a skeleton stepfile: one step per numbered item or second-level heading, each rule it states marked as a gate to write, and TODO markers where only an author can decide. stepgate_validate lists the markers left.
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | yes | The SKILL.md or SOP text, markdown with optional YAML frontmatter. |
No output schema declared.
No examples provided.
stepgate_submit Submit a step's output ~74
Submits the current step's output for a Stepgate run. Returns the next step, the gate failures to fix, or the finished run's outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| output | object | yes | The step's output, matching the schema the step gave. |
| run | string | yes | The run id a stepfile tool returned. |
No output schema declared.
No examples provided.
stepgate_try Try a draft stepfile ~93
Starts a run of a draft stepfile from its text, without adding it to the server. Drive it with stepgate_call and stepgate_submit. Drafts may call only public https URLs, and use only the credentials and settings the operator granted to drafts.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | yes | Inputs matching the draft's inputs schema. |
| stepfile | string | yes | The whole stepfile, as YAML or JSON text. |
No output schema declared.
No examples provided.
stepgate_validate Validate a draft stepfile ~62
Checks a draft stepfile against the schema and every load-time rule. Returns each issue with its path, or the stepfile's identity and whether stepgate_try accepts it.
| Name | Type | Req | Description |
|---|---|---|---|
| stepfile | string | yes | The whole stepfile, as YAML or JSON text. |
No output schema declared.
No examples provided.
What is the Stepgate MCP server?
Stepgate is an MCP server listed in the public MCP registry as io.github.Chaarangan/stepgate. Agents can't skip steps: runs gated stepfiles on the client's own model. This page covers its npm package (stepgate).
Is the Stepgate MCP server safe to use?
Stepgate scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Stepgate MCP server expose?
Stepgate exposes 8 tools: stepgate_call, stepgate_submit, stepgate_guide, stepgate_examples, stepgate_validate, and 3 more. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.
Is the Stepgate MCP server still maintained?
Stepgate is still listed as active in the MCP registry. We last reached this channel on 2 October 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 Stepgate MCP server under?
Stepgate 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.