SafeNode MCP Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAFENODE_API_KEY | Yes | Your SafeNode API key. Keys look like 'sn_...'. Set in the environment; it takes precedence over the config file. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echo back the text |
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 confusing it with others. The purpose of echoing text is completely distinct by default.
A single tool name 'echo' is trivially consistent, as there are no other names to deviate from. The name clearly reflects the action performed.
The server is named 'SafeNode MCP Gateway' but contains only a trivial echo tool, which is an extreme mismatch for the apparent scope. This is the definition of a single trivial tool.
The tool surface is severely incomplete for a gateway server, offering no functional operations beyond echoing input. There are obvious dead ends for any real workflow.