de en es ja ko ru zh

@igorromero/ciphersuite-mcp

Name: @igorromero/ciphersuite-mcp
Author: igorgrv1

by igorgrv1

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

ciphersuite-mcp

Un servidor MCP (Model Context Protocol) que proporciona herramientas de cifrado y descifrado AES-256-CBC, recursos que describen cada algoritmo y prompts listos para usar, todo ello ejecutable directamente en VS Code Copilot Chat.

Related MCP server: @erickwendel/ciphersuite-mcp

Qué hace

Capacidad	Nombre	Descripción
🔧 Herramienta	`encrypt_message`	Cifra cualquier mensaje de texto plano con una frase de contraseña
🔧 Herramienta	`decrypt_message`	Descifra un mensaje previamente cifrado con la misma frase de contraseña
📄 Recurso	`encryption://info`	Devuelve detalles sobre el algoritmo de cifrado, la derivación de la clave y el formato de salida
📄 Recurso	`decryption://info`	Devuelve cómo usar la herramienta de descifrado: formato esperado, reglas de la frase de contraseña y errores comunes
💬 Prompt	`encrypt_message_prompt`	Prompt predefinido que pide al agente que cifre un mensaje
💬 Prompt	`decrypt_message_prompt`	Prompt predefinido que pide al agente que descifre un mensaje

Cómo funciona el cifrado

Algoritmo: AES-256-CBC
Derivación de la clave: scrypt(passphrase, fixedSalt, 32) — puedes pasar cualquier cadena como frase de contraseña; el servidor deriva automáticamente una clave fuerte de 32 bytes
Formato de salida: <IV in hex>:<ciphertext in hex> — conserva la cadena completa para descifrarla más tarde
IV: se genera un IV aleatorio nuevo de 16 bytes en cada llamada de cifrado, por lo que el mismo mensaje cifrado dos veces produce una salida diferente

Requisitos previos

Node.js v24+ (consulta engines en package.json)

Instalación

npm install

No se necesita ningún paso de compilación: el servidor ejecuta TypeScript directamente mediante el soporte nativo de TypeScript de Node.js.

Uso en VS Code

1. Añadir la configuración del servidor MCP

Crea (o abre) .vscode/mcp.json en tu espacio de trabajo y añade:

{
  "servers": {
    "ciphersuite-mcp": {
      "command": "node",
      "args": ["--experimental-strip-types", "ABSOLUTE_PATH_TO_PROJECT/src/index.ts"]
    }
  }
}

o mediante npm:

{
  "servers": {
    "ciphersuite-mcp": {
      "command": "npx",
      "args": ["-y", "@igorromero/ciphersuite-mcp"]
    }
  }
}

Consejo: También puedes añadir este servidor a tu configuración de MCP a nivel de usuario en ~/.vscode/mcp.json para que esté disponible en todos los espacios de trabajo.

2. Recargar VS Code

Abre la paleta de comandos (Cmd+Shift+P) y ejecuta Developer: Reload Window (o simplemente reinicia VS Code).

3. Usarlo en Copilot Chat

Abre Copilot Chat (modo agente) y prueba:

Encrypt the message "Hello, World!" using the passphrase "my-secret-key"

Decrypt this message: a3f1...:<ciphertext> using the passphrase "my-secret-key"

Show me the encryption://info resource

El agente llamará automáticamente a la herramienta adecuada y devolverá el resultado.

Ejecutar el MCP Inspector

El MCP Inspector te permite explorar y probar todas las herramientas, recursos y prompts de forma interactiva en una interfaz de navegador:

npm run mcp:inspect

Esto abre el inspector en http://localhost:5173 y lo conecta al servidor en ejecución.

Ejecutar las pruebas

# Run all tests once
npm test

# Run tests in watch mode (with debugger)
npm run test:dev

La suite de pruebas cubre:

Cifrar un mensaje
Descifrar un mensaje con la frase de contraseña correcta
Listar y leer el recurso encryption://info
Obtener ambos prompts
Error: descifrar con la frase de contraseña incorrecta
Error: descifrar un texto cifrado malformado

Estructura del proyecto

src/
  index.ts   # Entry point — connects the server to stdio transport
  mcp.ts     # All tools, resources, and prompts are registered here
tests/
  mcp.test.ts

Scripts disponibles

Script	Descripción
`npm start`	Inicia el servidor (usado por los clientes MCP)
`npm run dev`	Inicia con observación de archivos e inspector de Node.js
`npm test`	Ejecuta todas las pruebas
`npm run test:dev`	Ejecuta las pruebas en modo de observación
`npm run mcp:inspect`	Abre la interfaz del MCP Inspector

Creación desde cero

Esta sección documenta cómo se construyó este servidor MCP paso a paso — algo útil para crear nuevos servidores MCP en el futuro.

Tipos de transporte de MCP

Existen 3 tipos de transporte de MCP:

Tipo	Clase	Descripción
`stdio`	`StdioServerTransport`	Se ejecuta localmente en la máquina — el más común para herramientas locales
`http`	—	Se ejecuta como una API sobre HTTP
`sse`	—	Server-Sent Events — procesa datos bajo demanda (streaming)

Dependencias

// package.json
"dependencies": {
  "@modelcontextprotocol/sdk": "^1.27.1",
  "@types/node": "^24.11.0",
  "zod": "^3.25.76"
}

1. Punto de entrada — `src/index.ts`

El punto de entrada crea un StdioServerTransport y conecta el servidor MCP a él:

// src/index.ts
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { server } from "./mcp.ts";

async function main() {
    const transport = new StdioServerTransport()
    await server.connect(transport)
    console.error('Encrypt MCP Server running on stdio')
}

main().catch((error) => {
    console.error("Fatal error in main():", error);
    process.exit(1);
});

2. Configuración del servidor — `src/mcp.ts`

Crea la instancia del servidor MCP con un nombre y una versión:

// src/mcp.ts
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";

export const server = new McpServer({
    name: '@igorromero/ciphersuite-mcp',
    version: '0.0.1'
})

3. Registrar herramientas

tools

Las herramientas son funciones que el LLM puede llamar para realizar acciones. Usa server.registerTool, que recibe 3 argumentos:

Nombre de la herramienta (cadena)
Objeto de configuración que contiene:
- description — qué hace la herramienta; el LLM usa esto para decidir cuándo llamarla
- inputSchema — equivalente al cuerpo de la solicitud, definido con Zod
- outputSchema — equivalente al cuerpo de la respuesta, definido con Zod
Función de controlador asíncrona — la implementación real

server.registerTool(
    'encrypt_message',
    {
        description: 'Encrypt a message',
        inputSchema: {
            message: z.string().describe("The message to encrypt"),
            encryptionKey: z.string().describe(
                "Any passphrase to use for encryption — the server derives a strong key from it automatically"
            )
        },
        outputSchema: {
            encryptedMessage: z.string().describe(
                "The encrypted message (format: iv:ciphertext)"
            )
        }
    },
    async ({ message, encryptionKey }) => {
        try {
            const encryptedMessage = encrypt(message, encryptionKey)
            return {
                content: [{ type: "text", text: encryptedMessage }],
                structuredContent: { encryptedMessage }
            }
        } catch (error) {
            return {
                isError: true,
                content: [{
                    type: 'text',
                    text: `Failed to encrypt message! Error: ${error instanceof Error ? error.message : String(error)}`
                }]
            }
        }
    }
)

El mismo patrón se aplica a decrypt_message — solo tienes que intercambiar los campos del esquema de entrada/salida y llamar a decrypt().

4. Registrar recursos

resource

Los recursos proporcionan información estática o calculada que ayuda al LLM a comprender el contexto de una herramienta. Usa server.registerResource, que recibe 4 argumentos:

Nombre del recurso
Plantilla de URI (normalmente igual al nombre)
Objeto de configuración que contiene una description
Función de controlador que devuelve contents — un array de objetos con uri, mimeType y text

server.registerResource(
    'encryption://info',
    'encryption://info',
    {
        description: 'Describes the encryption algorithm, key requirements, and output format used by this server',
    },
    () => ({
        contents: [
            {
                uri: "encryption://info",
                mimeType: "text/plain",
                text: `
Algorithm : AES-256-CBC
Key derivation: scrypt (passphrase + fixed server salt → 32-byte key)
Output format: <16-byte IV in hex>:<ciphertext in hex>  (separated by ":")
Notes:
  - Users pass any passphrase — the server derives a strong 32-byte key automatically using scrypt.
  - A random IV is generated for every encryption — the same message encrypted twice will produce different output.
  - Use the exact same passphrase to decrypt.
  - Keep the full "iv:ciphertext" string to decrypt later.
                `.trim(),
            },
        ]
    })
)

El recurso decryption://info sigue el mismo patrón y describe el formato de entrada esperado, los requisitos de la frase de contraseña y los escenarios de error comunes para la herramienta de descifrado.

5. Registrar prompts

prompt

Los prompts son plantillas de mensajes predefinidas que el LLM puede usar para invocar herramientas de forma guiada. Usa server.registerPrompt, que recibe 3 argumentos:

Nombre del prompt
Objeto de configuración que contiene:
- description — qué hace el prompt
- argsSchema — los parámetros de entrada, definidos con Zod
Función de controlador que devuelve messages — un array de objetos con role (user o assistant) y content

server.registerPrompt(
    "encrypt_message_prompt",
    {
        description: "Prompt to encrypt a plain-text message using the encrypt_message tool",
        argsSchema: {
            message: z.string().describe("The message to encrypt"),
            encryptionKey: z.string().describe(
                "Any passphrase to use for encryption — the server derives a strong key from it automatically"
            )
        }
    },
    ({ message, encryptionKey }) => ({
        messages: [
            {
                role: 'user',
                content: {
                    type: "text",
                    text: `Please encrypt the following message using the encrypt_message tool.\nMessage: ${message}\nEncryption key: ${encryptionKey}`,
                }
            }
        ]
    })
)

El decrypt_message_prompt sigue el mismo patrón — toma encryptedMessage y encryptionKey como argumentos e indica al LLM que llame a decrypt_message.

6. Conexión del servidor MCP a un IDE

VS Code (automático)

Crea .vscode/mcp.json en la raíz del proyecto. VS Code lo detectará automáticamente:

{
    "servers": {
        "ciphersuite-mcp": {
            "command": "node",
            "args": [
                "--experimental-strip-types",
                "src/index.ts"
            ]
        }
    }
}

Otros IDEs / Otros proyectos

Copia la entrada del servidor ciphersuite-mcp en el archivo de configuración de MCP del proyecto o IDE de destino. El servidor se ejecuta como un subproceso mediante stdio, por lo que cualquier cliente compatible con MCP puede conectarse a él.

Available Tools

2 tools

decrypt_messageA

Decrypt a message that was encrypted with the encrypt_message tool

Name	Required	Description	Default
`encryptionKey`	Yes	The same passphrase used during encryption
`encryptedMessage`	Yes	The encrypted message (format: iv:ciphertext)

Output Schema

Name	Required	Description
`decryptedMessage`	Yes	The decrypted plain-text message

TDQS

A3.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It does not state whether the operation is read-only, has side effects, or what happens on failure (e.g., wrong key). The only behavioral detail is the requirement for the same passphrase, which partially addresses input constraints but not the tool's overall safety profile. This is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with zero filler. It states the verb, object, and connection to the sibling tool efficiently, making it easy to scan and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, full parameter coverage, and presence of an output schema, the description is mostly complete. It correctly identifies the key requirement and relationship to encrypt_message. However, lacking behavioral disclosure (e.g., error handling, purity) means it is not fully complete for an agent deciding to invoke it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter already has a description. The tool description adds minimal semantic value beyond mentioning the key matches encrypt_message, which mirrors what the schema already states. This meets the baseline for full schema coverage but does not provide additional meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Decrypt') and resource ('a message'), and explicitly ties it to the encrypt_message tool, which differentiates it from the sibling. It is not a tautology; it names the exact operation and its counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly implies usage context by referencing encrypt_message, indicating it is the decryption counterpart. However, it does not explicitly state when not to use it or name alternative tools beyond the implicit sibling relationship. This is clear context but lacks explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

encrypt_messageC

Encrypt a message

Name	Required	Description	Default
`message`	Yes	The message to encrypt
`encryptionKey`	Yes	Any passphrase to use for encryption — the server derives a strong key from it automatically

Output Schema

Name	Required	Description
`encryptedMessage`	Yes	The encrypted message (format: iv:ciphertext)

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden for behavioral disclosure, but it only states the action. It does not mention that encryption is irreversible (without the key), the output format, or any side effects. The schema hints at key derivation, but the description itself adds no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, but it essentially restates the tool name without adding operational detail. While not verbose, it doesn't earn its place beyond the name—acceptable but minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema existing, the description is too sparse for an encryption operation. It lacks information about when encryption is appropriate, the nature of the output, or any warnings. The agent is left to infer everything from the schema and sibling naming, which is insufficient for correct invocation in varied contexts.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for both parameters, so the schema already documents 'message' and 'encryptionKey' with meaningful descriptions. The tool description adds no extra parameter information, but the baseline is 3 given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Encrypt a message') with a specific verb and resource. It implicitly distinguishes from the sibling tool 'decrypt_message' by focusing on encryption, though it doesn't explicitly name the alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus decrypt_message or any other context. There is no mention of prerequisites, security considerations, or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesv0.0.1Aug 27, 2026
- First observeddecrypt_message
- First observedencrypt_message

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.6/5.0

Scored 2026-08-27 00:30 across 2 tools

Disambiguation5/5

The two tools are perfectly distinct: one encrypts, the other decrypts. There is no overlap or potential for confusion between them.

Naming Consistency5/5

Both tools follow the same verb_noun pattern: encrypt_message and decrypt_message. Naming is consistent and intuitive.

Tool Count4/5

At only 2 tools, the server is minimal, but the domain of encryption/decryption inherently requires exactly these two operations. The count is slightly under the typical 3-15 range but perfectly appropriate for its narrow scope.

Completeness5/5

The tool surface covers the full encryption/decryption lifecycle with no missing operations. For a cipher suite, encrypt and decrypt are the only necessary functions.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

Related MCP Connectors

Prompeteer AOAuth
ai.prompeteer
Generate contextual prompts and reusable agent skills, evaluate prompts with the 16-dimension Prompt Score, and manage saved work in PromptDrive. Twelve MCP tools also provide authorized access to private Memory for source-grounded answers. Connect over Streamable HTTP using OAuth 2.1 and PKCE. Generation consumes account quota and automatically saves successful results; Memory access follows account permissions and plan limits.
App Automation Developer Tools Product Management
123
https://prompeteer.ai/mcp
secureflows-mcp A
io.github.michal-lefler
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Code Analysis Developer Tools Security
181
https://www.secure-flows.com/mcp
mcp-serverOAuth
com.niftypm
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Project Management Communication File Systems
2
https://mcp.niftypm.com/mcp
SRIFT A
app.srift
Secure P2P File Transfer, Encrypted Chat & Communication | Decentralized P2P & AES-256-GCM encryption | Zero cloud logs. Zero registration. For humans and autonomous AI agents / MCP servers.
Communication File Systems Networking & Infrastructure
92
https://srift.app/mcp

Related MCP Servers

Kova Mind MCP Serverofficial
Knowledge & Memory Security
KovaMind
A
license
A
quality
C
maintenance
Enables AI memory persistence and secure credential management via vault tools for MCP-compatible clients like Claude Desktop, Cursor, and VS Code.
Updated 3 months ago (2026-08-12 02:29 UTC)
12
11 npm
MIT
@erickwendel/ciphersuite-mcp
Security
PabloBorgesMartins
A
license
A
quality
C
maintenance
Provides AES-256-CBC encryption and decryption tools, a resource for algorithm details, and prompts for encrypting and decrypting messages, all runnable inside VS Code Copilot Chat.
Updated 2 months ago (2026-08-18 20:19 UTC)
2
ISC
@erickwendel/ciphersuite-mcp
Developer Tools
tbatista86
A
license
C
quality
C
maintenance
Provides AES-256-CBC encryption and decryption tools, an algorithm info resource, and ready-to-use prompts for use in MCP-compatible clients like VS Code Copilot Chat.
Updated 2 months ago (2026-09-13 13:34 UTC)
1
ISC
ciphersuite-mcp
Security Developer Tools
giovaninogueira
A
license
C
quality
C
maintenance
Enables encrypting and decrypting plain-text messages with AES-256-CBC using any passphrase, with automatic scrypt key derivation and a fresh random IV per call. It also exposes a resource describing the algorithm and ready-to-use prompts, and can be run directly inside VS Code Copilot Chat or the MCP Inspector.
Updated a month ago (2026-09-13 14:18 UTC)
2
ISC

ciphersuite-mcp

Qué hace

Cómo funciona el cifrado

Requisitos previos

Instalación

Uso en VS Code

1. Añadir la configuración del servidor MCP

2. Recargar VS Code

3. Usarlo en Copilot Chat

Ejecutar el MCP Inspector

Ejecutar las pruebas

Estructura del proyecto

Scripts disponibles

Creación desde cero

Tipos de transporte de MCP

Dependencias

1. Punto de entrada — src/index.ts

2. Configuración del servidor — src/mcp.ts

3. Registrar herramientas

4. Registrar recursos

5. Registrar prompts

6. Conexión del servidor MCP a un IDE

VS Code (automático)

Otros IDEs / Otros proyectos

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Kova Mind MCP Serverofficial

@erickwendel/ciphersuite-mcp

@erickwendel/ciphersuite-mcp

ciphersuite-mcp

1. Punto de entrada — `src/index.ts`

2. Configuración del servidor — `src/mcp.ts`