VaultMesh Architect MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRY_RUN | No | If true, anchoring returns simulated receipts, no chain calls | true |
| VM_WORKDIR | No | To direct outputs to a specific path without changing the process CWD | |
| BTC_RPC_URL | No | Bitcoin RPC URL (only used if DRY_RUN=false) | |
| ETH_RPC_URL | No | Ethereum RPC URL (only used if DRY_RUN=false) | |
| RFC3161_URL | No | TSA endpoint (only used if DRY_RUN=false) | |
| MCP_HEARTBEAT | No | Enable stderr heartbeat logging | |
| MCP_HEARTBEAT_MS | No | Heartbeat interval in milliseconds | 30000 |
| LAWCHAIN_PRIVATE_KEY_PEM | No | Ed25519 PEM for signing LAWCHAIN entries and capabilities. If absent, an ephemeral key is generated per process |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |