nodus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODUS_MCP_URL | No | Upstream MCP server URL. Only plain-HTTP URLs using exact loopback hostnames and /mcp path are accepted. | http://127.0.0.1:4319/mcp |
| NODUS_MCP_TOKEN | No | Bearer token for authenticating to Nodus MCP server. | |
| NODUS_MCP_TOKEN_FILE | No | Path to a JSON file containing a 'token' field. |
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 |
|---|---|
| nodus_gateway_healthA | Check whether the Nodus MCP server is reachable and authenticated. Never errors. |
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 other operations. Its purpose as a health/readiness check is clear and unambiguous.
The single tool name is clear, descriptive, and follows a consistent hierarchical pattern with the server prefix. There are no mixed conventions to cause confusion.
A lone health-check tool is a trivial surface for an MCP server. Even as a gateway utility, it provides almost no functional value and appears extremely under-scoped.
The server exposes only a health check, so no substantive domain operations exist. Any real workflow would dead-end immediately after confirming reachability.