MCP Server with Authentication
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JWT_SECRET | No | Secret key for JWT token generation and verification (used with JWT server). | |
| MCP_API_KEY | No | API key for authentication (used with API key server). Can also be passed via arguments or metadata. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoC | Echo a simple message (no authentication required) |
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
Only one tool exists, so there is no risk of confusion between tools.
With a single tool named 'echo', naming consistency is trivially maintained.
A server named 'MCP Server with Authentication' should have multiple tools related to authentication, but instead it has only one trivial echo tool.
The server's name suggests a focus on authentication, yet the tool surface is limited to echoing messages, leaving the entire authentication domain uncovered.