MCP server · Digital Asset
digital-asset
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
⚠ Proposed MCP surface. No official hosted MCP server was found for Digital Asset. The tools below are a candidate set derived from this provider's API, and the link points at the source descriptor rather than a live server. If Digital Asset publishes an official server, this page will update to it on the next build.
Descriptor
Candidate descriptor · transport http
Tools
get_allocation_factory— Get the factory and choice context for creating allocations using the `AllocationFactory_Allocate` choice.get_allocation_transfer_context— Get the choice context to execute a transfer on an allocation.get_allocation_withdraw_context— Get the choice context to withdraw an allocation.get_allocation_cancel_context— Get the choice context to cancel an allocation.get_registry_info— Get information about the registry. The response includes the standards supported by the registry.list_instruments— List all instruments managed by this instrument admin.get_instrument— Retrieve an instrument's metadata.get_transfer_factory— Get the factory and choice context for executing a direct transfer.get_transfer_instruction_accept_context— Get the choice context to accept a transfer instruction.get_transfer_instruction_reject_context— Get the choice context to reject a transfer instruction.get_transfer_instruction_withdraw_context— Get the choice context to withdraw a transfer instruction.get_open_api_spec— (no description published in the spec)get_operator— (no description published in the spec)get_all_packages— (no description published in the spec)get_all_instrument_configurations— (no description published in the spec)get_instrument_configuration— (no description published in the spec)get_mint_offer_create_context— Get the factory and choice context for creating a mint offer.get_mint_request_create_context— Get the factory and choice context for creating a mint request.get_burn_offer_create_context— Get the factory and choice context for creating a burn offer.get_burn_request_create_context— Get the factory and choice context for creating a burn request.get_mint_offer_accept_context— Get the choice context to accept and execute a mint offer.get_mint_offer_reject_context— Get the choice context to reject a mint offer.get_mint_offer_cancel_context— Get the choice context to cancel a mint offer.get_mint_request_accept_context— Get the choice context to accept and execute a mint request.get_mint_request_reject_context— Get the choice context to reject a mint request.get_mint_request_cancel_context— Get the choice context to cancel a mint request.get_burn_offer_accept_context— Get the choice context to accept and execute a burn offer.get_burn_offer_reject_context— Get the choice context to reject a burn offer.get_burn_offer_cancel_context— Get the choice context to cancel a burn offer.get_burn_request_accept_context— Get the choice context to accept and execute a burn request.get_burn_request_reject_context— Get the choice context to reject a burn request.get_burn_request_cancel_context— Get the choice context to cancel a burn request.get_burn_mint_factory— Get the burn mint factory and choice context for burn and mint.verify_transfer_proof— Verify the outcome of a transfer of Registry Utility assets on Canton. Given an UpdateID and a Transfer Object, the service looks up the corresponding ledger transaction and verifies the transfer details against the on-chain events. The response status indicates the transfer outcome: - `Success`: The transfer was executed in the referenced transaction - `Pending`: The transfer instruction has been created but not yet settled - `Failure`: The transfer instruction was rejected or withdrawn by one of the parties If none of the above conditions are met, if the provided transfer details do not match the on-chain data, or if the original TransferInstruction contract cannot be retrieved, a `400` is returned. No further diagnostic information is included in the error response to prevent unintended disclosure of sensitive ledger data.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.