@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_messageB | Encrypts a message |
| decrypt_messageB | Decrypts an encrypted message |
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 2 tools
The two tools have clearly distinct purposes: one encrypts and one decrypts. No overlap or ambiguity exists between them.
Both tool names follow the same verb_noun pattern: encrypt_message and decrypt_message. This is consistent and predictable.
With only 2 tools, the server feels thin for the scope of a cipher suite. It is borderline, as the tools are focused but minimal.
The server covers the basic encrypt/decrypt lifecycle, but lacks key management, algorithm selection, or other common cipher operations. For a cipher suite, this is a minimal surface.