CIMS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CIMS_ADAPTER | No | Adapter to use. 'mock' (default) for in-memory demo, 'live' for the Roots CIMS relay. | mock |
| CIMS_API_KEY | No | API key for the Roots CIMS relay. Required when CIMS_ADAPTER is 'live'. | |
| CIMS_RELAY_URL | No | URL of the Roots CIMS relay. Required when CIMS_ADAPTER is 'live'. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cims_validate_idA | Check whether a string is a well-formed CIMS ID (R-institution-account) and parse its parts. Pure format check; does not hit the directory. |
| cims_resolveA | Resolve a legal name, handle, or CIMS ID (R-institution-account) to a routable party. Refuses raw 0x addresses. |
| cims_institutionA | Look up a CIMS institution by index (e.g. "233" from R-233-2993204): active status, supported rails, and attestation policy. Check before routing to an unfamiliar institution. |
| cims_quoteA | Price and policy-check a transfer (name check, AML, attestation requirement). Does not move funds. Prefer delayed mode for first-time or large payments. Show the quote to the user before calling cims_send. |
| cims_sendA | Create a CIMS intent from a quote. Requires confirm=true and must only be called after the user has reviewed the quote. May return attestation_required if institution policy demands it. |
| cims_attestA | Approve or reject an intent in attestation_required state (institution operator action). Approving moves it to pending; rejecting reverts it. |
| cims_cancelA | Cancel a pending or attestation_required intent inside the cancel window. |
| cims_statusA | Get intent status: pending, attestation_required, finalized, cancelled, reverted. Includes cancel window and tx hash when finalized. |
| cims_list_intentsB | List known intents, optionally filtered by status and/or asset. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cims-send-money | Guided, safe transfer flow: resolve, quote, confirm with user, send, track. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| cims-overview | What CIMS is, ID format, transfer modes, and the safety model. |
| cims-lifecycle | Status transition diagram and timing windows for CIMS intents. |
TDQS
Scored across 9 tools
Each tool maps to a distinct step in the CIMS workflow: validation, resolution, institution lookup, quoting, sending, attestation, cancellation, status, and listing. Potentially adjacent pairs like validate_id/resolve and quote/send are clearly separated by their descriptions.
All tools share the cims_ prefix and mostly use concise action-oriented names. Minor inconsistencies exist: cims_institution and cims_status are noun-only lookups, while cims_quote is ambiguous between noun and verb, so the pattern is not perfectly uniform.
Nine tools is well-scoped for a payment-intent lifecycle with supporting identity and institution lookup operations. Each tool covers a distinct operation without redundancy or unnecessary bloat.
The set covers the full path from ID validation, party resolution, and institution discovery through quote, send, attestation, cancellation, status, and listing. State transitions are represented, and there are no obvious dead ends in the core workflow.