AramidBridgeMCP
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 |
|---|---|
| get_supported_assetsA | List assets supported by the Aramid Bridge with available routes between Voi and Algorand. Each asset includes source/destination token IDs and types. Optionally filter by source chain. |
| bridge_txnA | Build an unsigned Aramid Bridge transaction for bridging assets between Voi and Algorand. Supports native tokens (VOI/ALGO) and ASAs. The 0.1% bridge fee is deducted automatically. Delivery is automatic on AVM destinations. Returns base64-encoded transaction (string[]) for wallet signing via UluWalletMCP. |
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
get_supported_assets is a read-only query for available assets and routes; bridge_txn is a transaction builder. Their purposes are clearly distinct with no overlap, so an agent can easily select the right tool.
Both tools use snake_case with a consistent verb_noun pattern: get_supported_assets and bridge_txn. The abbreviation 'txn' is minor and does not break the pattern.
Only 2 tools are provided, which is below the typical 3-15 range. While each tool earns its place for a minimal bridge service, the count feels thin for a production bridging MCP.
The surface covers asset discovery and transaction building but lacks tools for checking bridge status, estimating fees, or retrieving transaction history. These are notable gaps for a bridge lifecycle, though signing is delegated to UluWalletMCP.