Security
Verify the Ed25519 signature attached to an AGEX bundle
Call this tool from your code in three languages.
# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/agex-signature-verifier' \
-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/agex-signature-verifier' \
-F 'bundleFile=/public/processing/example.agex.json' \
-F 'signerPublicKey=BASE64_PUBLIC_KEY'Send a POST request with your inputs as JSON. File parameters require a separate upload first.
POST https://api.elysiatools.com/en/api/tools/agex-signature-verifier| Name | Type | Required | Description |
|---|---|---|---|
| bundleFile | fileupload required | Yes | — |
| signerPublicKey | textarea | No | — |
JSON result
{
"key": {...},
"metadata": {
"key": "value"
},
"error": "Error message (optional)",
"message": "Notification message (optional)"
}Add this tool to your Model Context Protocol server so AI agents can list and call it.
Add this block to your MCP client configuration:
{
"mcpServers": {
"elysiatools-agex-signature-verifier": {
"name": "agex-signature-verifier",
"description": "Verify the Ed25519 signature attached to an AGEX bundle",
"baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=agex-signature-verifier",
"command": "",
"args": [],
"env": {},
"isActive": true,
"type": "sse"
}
}
}After connecting to the SSE endpoint, list the exposed tools:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}Invoke the tool by its id, passing arguments built from its parameters:
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "agex-signature-verifier",
"arguments": {
"bundleFile": "/public/processing/example.agex.json",
"signerPublicKey": "BASE64_PUBLIC_KEY"
}
}
}Questions or issues? Contact [email protected]