s-gw
NPM · @S-GW/S-GW · SCANNED SEP 21
Keep credentials out of AI coding agents with local approvals, scoped injection, and audit trails.
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 Security99
- 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
- 61 of 235 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 sgateway/s-gw). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 38 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 450 tokens (~56/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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "sgw_execute_request" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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 s-gw MCP server?
s-gw runs locally as an npm package, launched with npx -y @s-gw/s-gw. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @s-gw/s-gw
claude mcp add sgateway-s-gw -- npx -y @s-gw/s-gw
{
"mcpServers": {
"sgateway-s-gw": {
"command": "npx",
"args": [
"-y",
"@s-gw/s-gw"
]
}
}
} {
"servers": {
"sgateway-s-gw": {
"command": "npx",
"args": [
"-y",
"@s-gw/s-gw"
]
}
}
} codex mcp add sgateway-s-gw -- npx -y @s-gw/s-gw
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sgateway-s-gw": {
"type": "local",
"command": [
"npx",
"-y",
"@s-gw/s-gw"
],
"enabled": true
}
}
} openclaw mcp add sgateway-s-gw --command npx --arg -y --arg @s-gw/s-gw
mcp_servers:
sgateway-s-gw:
command: "npx"
args: ["-y", "@s-gw/s-gw"] {
"McpServers": {
"sgateway-s-gw": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@s-gw/s-gw"
]
}
}
} assistant mcp add sgateway-s-gw -t stdio -c npx -a -y @s-gw/s-gw
{
"mcpServers": {
"sgateway-s-gw": {
"command": "npx",
"args": [
"-y",
"@s-gw/s-gw"
]
}
}
} 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.
- 21 Sept 26 +1
- Package version: 0.1.19 → 0.1.21 functional
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 14 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
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 21 Sept 2026 · Analysed npm/@s-gw/s-gw@0.1.21
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 | sgateway/s-gw |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sgateway/s-gw/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2448044592 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e633dec26b2cddcdc79f8c56c5851bb081cbb903df6d80b661115c4e8d22c6aa2956abb3594b1135e14702c46defc3ada10636f7f754d3c4a3b5fba7d |
Background: How many MCP packages publish verified provenance →
Dependencies 235 packages
| Packages resolved | 235 |
|---|---|
| Stale | 61 |
| 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 →
sgw_describe_handle Describe Handle ~28
Show non-secret metadata for one local secret handle.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
No output schema declared.
No examples provided.
sgw_execute_request Execute Approved Request ~29
Execute a previously approved local request and return sanitized output.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
No output schema declared.
No examples provided.
sgw_list_handles List Handles ~20
List known local secret handles and non-secret metadata.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sgw_request_execution Request Secret-Backed Execution ~87
Create a pending local manifest for a command that needs one secret injected as an environment variable.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | – |
| command | string | yes | – |
| env | array | – | – |
| handle | string | yes | – |
| injectEnv | string | yes | – |
| reason | string | – | – |
| timeoutMs | integer | – | – |
| workingDir | string | – | – |
No output schema declared.
No examples provided.
sgw_request_ssh_session Request s-gw-Owned SSH Session ~108
Create a local approval request for an SSH command. Unix-like systems use an s-gw-owned ControlMaster; Windows uses a hardened one-shot ssh.exe command with an SSH private key.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | – |
| handle | string | yes | – |
| injectEnv | string | – | – |
| port | integer | – | – |
| reason | string | – | – |
| target | string | yes | – |
| timeoutMs | integer | – | – |
| workingDir | string | – | – |
No output schema declared.
No examples provided.
sgw_run_execution Run Secret-Backed Execution ~85
Run a command through reusable local approval without creating a ledger record for every invocation.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | – |
| command | string | yes | – |
| env | array | – | – |
| handle | string | yes | – |
| injectEnv | string | yes | – |
| reason | string | – | – |
| timeoutMs | integer | – | – |
| workingDir | string | – | – |
No output schema declared.
No examples provided.
sgw_scan_file Scan Local File ~45
Scan a local file for secrets and return tokenized text plus local handles. Raw values are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| persist | boolean | – | – |
No output schema declared.
No examples provided.
sgw_scan_text Scan Text ~48
Scan supplied text and return tokenized text. Persist=false previews handles without enrolling secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| persist | boolean | – | – |
| source | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
What is the s-gw MCP server?
s-gw is an MCP server listed in the public MCP registry as io.github.sgateway/s-gw. Keep credentials out of AI coding agents with local approvals, scoped injection, and audit trails. This page covers its npm package (@s-gw/s-gw).
Is the s-gw MCP server safe to use?
s-gw scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 s-gw MCP server expose?
s-gw exposes 8 tools: sgw_scan_file, sgw_scan_text, sgw_list_handles, sgw_describe_handle, sgw_request_execution, and 3 more. Their descriptions and schemas cost roughly 450 tokens of context every time the server is loaded.
Is the s-gw MCP server still maintained?
s-gw is still listed as active in the MCP registry. We last reached this channel on 21 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 s-gw MCP server under?
s-gw 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.