s-gw MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sgw_scan_fileA | Scan a local file for secrets and return tokenized text plus local handles. Raw values are not returned. |
| sgw_scan_textB | Scan supplied text and return tokenized text. Persist=false previews handles without enrolling secrets. |
| sgw_list_handlesA | List known local secret handles and non-secret metadata. |
| sgw_describe_handleB | Show non-secret metadata for one local secret handle. |
| sgw_request_executionC | Create a pending local manifest for a command that needs one secret injected as an environment variable. |
| sgw_request_ssh_sessionC | Create a local approval request for an SSH command that s-gw will run over its own persistent ControlMaster session. |
| sgw_execute_requestC | Execute a previously approved local request and return sanitized output. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Tools have distinct purposes, but there is potential confusion between sgw_request_execution and sgw_execute_request (create vs. execute), and the names are similar. However, descriptions clarify the difference, and other tools are clearly distinct.
All tool names follow a consistent 'sgw_verb_noun' pattern using snake_case. Each name clearly indicates the action and target, with no deviations.
With 7 tools covering scanning, handle management, execution requests, and SSH sessions, the count is well-scoped for a security-focused server. Each tool has a clear role.
The set covers core workflows (scan, request, execute, list handles) but lacks tools for managing pending requests (e.g., list, approve, cancel) or SSH sessions after creation (e.g., list, end), leaving notable gaps.