mcp-gateway-scan
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 |
|---|---|
| scan_gatewayA | Read-only static scan of a repo/directory across 7 gateway-readiness dimensions (RBAC, fail-close, supply-chain pinning, observability, routing/cost, secrets, prod-readiness). Returns a per-dimension 🟢🟡🔴 summary plus the structured result. Never executes target code; secret values are redacted (location only, never the value). |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly described and distinct from any other potential tools.
The single tool name 'scan_gateway' follows a clear verb_noun pattern. Naming consistency is perfect as there is only one name.
One tool for a domain that covers 7 dimensions feels slightly thin; a more granular breakdown into separate tools for each dimension might improve flexibility, but the single tool is comprehensive.
The tool covers all 7 gateway-readiness dimensions comprehensively, providing a full static scan without obvious gaps. It is read-only, which is appropriate for scanning.