@erickwendel/ciphersuite-mcp
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 |
|---|---|
| encrypt_messageC | Encrypts a message using a passphrase |
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 or overlap with other tools. The tool's purpose is clearly defined as encrypting a message with a passphrase.
The single tool name 'encrypt_message' follows a clear verb_noun pattern, which is consistent. However, with only one tool, there is no broader pattern to evaluate, so a perfect score is not fully justified.
A single tool for a 'ciphersuite' server is extremely thin. A cipher suite typically involves encryption, decryption, key management, and possibly hashing, so one tool feels inadequate for the stated domain.
The server only supports encryption, leaving out decryption, key generation, and other essential operations. This is a severely incomplete surface for a cipher suite, as users cannot reverse the operation or manage keys.