Security

Age-like Encrypted File Bundle

Encrypt or decrypt portable password-based file bundles with Argon2id, XChaCha20-Poly1305, and optional signatures

json· JSON resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/age-like-encrypted-file-bundle' \
  -F 'file=@/path/to/sourceFile.ext'
curl -X POST 'https://api.elysiatools.com/upload/age-like-encrypted-file-bundle' \
  -F 'file=@/path/to/bundleFile.ext'

# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/age-like-encrypted-file-bundle' \
  -F 'operation=encrypt' \
  -F 'sourceFile=/public/samples/mp3/waterfall.mp3' \
  -F 'bundleFile=/path/to/file.ext' \
  -F 'passphrase=correct horse battery staple' \
  -F 'strength=moderate' \
  -F 'includeSignature=false' \
  -F 'signerId=Optional signer label, e.g. ops-key-1' \
  -F 'signerPrivateKey=Optional base64 Ed25519 secret key. Leave blank to auto-generate when signing.' \
  -F 'signerPublicKey=Optional base64 Ed25519 public key for signature verification during decrypt'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/age-like-encrypted-file-bundle

Parameters

Name	Type	Required	Description
operation	select	Yes	—
sourceFile	fileupload required	No	—
bundleFile	fileupload required	No	—
passphrase	text	Yes	—
strength	select	Yes	—
includeSignature	checkbox	No	—
signerId	text	No	—
signerPrivateKey	textarea	No	—
signerPublicKey	textarea	No	—

File-type parameters must be uploaded first via POST /upload/age-like-encrypted-file-bundle, then the returned filePath is passed to the corresponding file field.

Response format

JSON result

JSON

{
  "key": {...},
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-age-like-encrypted-file-bundle": {
      "name": "age-like-encrypted-file-bundle",
      "description": "Encrypt or decrypt portable password-based file bundles with Argon2id, XChaCha20-Poly1305, and optional signatures",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=age-like-encrypted-file-bundle",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "age-like-encrypted-file-bundle",
    "arguments": {
  "operation": "encrypt",
  "sourceFile": "/public/samples/mp3/waterfall.mp3",
  "bundleFile": "https://example.com/file.ext",
  "passphrase": "correct horse battery staple",
  "strength": "moderate",
  "includeSignature": false,
  "signerId": "Optional signer label, e.g. ops-key-1",
  "signerPrivateKey": "Optional base64 Ed25519 secret key. Leave blank to auto-generate when signing.",
  "signerPublicKey": "Optional base64 Ed25519 public key for signature verification during decrypt"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]