Aries
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUBFROST_RPC | No | Optional gateway override for JSON-RPC (default mainnet). | |
| SUBFROST_REST | No | Optional gateway override for REST (default mainnet). | |
| SUBFROST_API_KEY | Yes | Required — auth for the live chain-data tools. | |
| ARIES_INCIDENTS_PATH | No | Optional path for local incident store (default data/incidents.jsonl). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aries_searchC | Search the Alkanes + Subfrost documentation corpus (protocol docs, Subfrost API/JSON-RPC reference, alkanes-rs CLI, step-by-step tutorials, oracle docs, reference contracts). Returns path + heading + preview for each hit. Call aries_doc next to read a section. |
| aries_docA | Read a corpus doc token-efficiently. Without |
| aries_full_docB | Return the complete, untruncated markdown of a corpus doc by path. Use when you need the whole file in one shot. |
| aries_catalogA | List every doc in the corpus grouped by source (subfrost, subfrost-api, alkanes-rs, tutorials, oracles, orddao, reference). |
| aries_tutorialsA | List the step-by-step Alkanes/Subfrost tutorials available in the corpus (title, summary, read-time, doc path). Use this to pick the right tutorial for a build task, then read it with aries_doc (TOC-first) or aries_full_doc. Covers making/deploying/auditing contracts, tokens, DAOs, oracles, stablecoins, AMMs, wrapped BRC-20, frBTC/Subfrost, DIESEL, swapping, indexers, and security. |
| aries_tokens_by_addressA | List all Alkanes tokens held by a Bitcoin address (wraps alkanes_protorunesbyaddress, protocolTag is always 1). Returns outpoints and the rune balances at each. Note: very high-activity addresses (thousands of UTXOs, e.g. the frBTC treasury) can exceed the RPC timeout. |
| aries_contract_metaA | Get an Alkanes contract's metadata (name, symbol, decimals, totalSupply) by its alkane id {block, tx}, via the alkanes_meta view. String id form is block:tx. Note: some contracts (incl. frBTC 32:0) do not implement the meta view and will error — for those, read fields via aries_simulate opcodes (or use aries_frbtc_status for frBTC). |
| aries_bytecodeA | Fetch the raw WASM bytecode (hex) of an Alkanes contract by {block, tx}. For human-readable disassembly, pair with the |
| aries_simulateB | Simulate an Alkanes view call against a contract without broadcasting — the way to read contract state by invoking an opcode. Pass the full simulation request object. The opcode goes in |
| aries_frbtc_statusA | Convenience: fetch frBTC (alkane 32:0) name, symbol, decimals, total supply, and current signer in one call. Good for 'is the peg live / who is the signer / how much frBTC exists' questions. |
| aries_oracle_readA | Read a value from a deployed Alkanes oracle contract via a staticcall-safe view (alkanes_simulate). Give the oracle's alkane id {block,tx}, the read opcode, and any inputs (u128 each). |
| aries_oracle_priceA | Read the latest price from a Chainlink-style Alkanes price-feed oracle (opcode 10 = GetPrice). Give the oracle alkane id {block,tx} and the symbolId. Returns priceE8 (raw 1e8-scaled u128), price (number), priceBlock, updatedBlock, and ageBlocks (vs current height). Needs a deployed price-feed instance — the feed is a template (see reference/oracles.md), so pass the id you want to read. |
| aries_tokenA | Read any Alkanes token's metadata (name, symbol, decimals, totalSupply) by its alkane id {block, tx} via opcode views — works when alkanes_meta does not. Detects supply at opcode 105 (frBTC-style) or 101 (orbital/NFT-style) and flags supply-1 tokens as likely Orbitals. |
| aries_diesel_statusA | Convenience: read DIESEL — the Alkanes genesis token at 2:0 (the base token most contracts pair against) — name, symbol, decimals, and totalSupply in one call. |
| aries_poolsA | List Alkanes AMM liquidity pools with details (reserves, TVL, 24h volume, trending) for a factory, via the Subfrost REST API (get-all-pools-details). |
| aries_pool_infoA | Get details (reserves, token pair, price) for one Alkanes AMM pool via the Subfrost REST API (get-pool-details). Give the pool's alkane id as block:tx; |
| aries_rpcA | Escape hatch: call any read-only Subfrost gateway method directly (esplora_*, ord_*, metashrew_*, alkanes_*, brc20_*, and read-only btc_get*/btc_decode*). Write/broadcast methods are blocked. Use the docs tools to find method names and params. |
| aries_constantsA | Return the key Alkanes/frBTC constants instantly: frBTC contract id, wrap/unwrap/get-signer opcodes, genesis block, protocol tag. |
| aries_scaffoldA | Return a scaffold/recipe: 'wrap' (mint frBTC protostone), 'unwrap' (burn frBTC), 'contract' (alkanes-rs WASM contract skeleton), or 'orbital' (Alkanes NFT / Orbital contract skeleton — a Token with supply 1 + opcode 1000 media). These are starting templates, not audited code. |
| aries_incident_reportA | Record a mistake, bug, rule violation, or pitfall you hit while working with Alkanes/Subfrost, so future sessions can learn from it. File one whenever you make an error worth not repeating, hit a surprising behaviour, or learn a non-obvious gotcha — contributing makes Aries smarter for every user. Submissions enter a review queue and become searchable once an operator approves them. SECURITY: never include secrets, API keys, seed phrases, private keys, local file paths, or hostnames — reports are treated as shareable; use placeholders like . (Inputs are also auto-sanitized on the way in.) |
| aries_incident_queryA | Query the TRUSTED incident corpus to avoid repeating known mistakes — call this BEFORE non-trivial Alkanes/Subfrost work. Serves only operator-vetted incidents (pending submissions are not returned). actions: recent (newest first, default), search (free-text + filters), stats (aggregate counts), get (by incident id). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bitbragi/alkanes-aries'
If you have feedback or need assistance with the MCP directory API, please join our Discord server