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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| encrypt_messageC | Encrypts a message |
| decrypt_messageC | Decrypts a message |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| encrypt_message_prompt | Prompt to encrypt a message a plain text message using the encrypt_message tool |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| encryption://info | Provides information about the encryption tools available in this MCP. |
TDQS
Scored across 2 tools
The two tools have perfectly distinct, complementary purposes: one encrypts and one decrypts. There is no realistic way an agent could confuse them.
Both names follow the same clean verb_noun pattern (encrypt_message, decrypt_message), with consistent snake_case and parallel structure.
Two tools is on the thin side for a server billed as a 'ciphersuite,' which implies more than a single symmetric pair. The count is defensible for a minimal encrypt/decrypt service but feels under-scoped.
Core encrypt/decrypt is covered, but a cipher suite typically also needs key generation/management, algorithm selection, and possibly hashing or sign/verify. These notable gaps mean agents cannot perform a full crypto lifecycle.