Back to Browse

Cloud Wallet MCP Server

FinanceLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

EVM wallet reads, simulation, and transaction execution under user-defined authorization policies.

About

EVM wallet reads, simulation, and transaction execution under user-defined authorization policies.

Remote endpoints: streamable-http: https://cloud.ekubo.org/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-ekuboprotocol-cloud-wallet": {
      "url": "https://cloud.ekubo.org/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Cloud Wallet by Ekubo

Cloud Wallet is a hosted EVM wallet that lets AI agents read account data, simulate transactions, and request transaction execution under rules chosen by the owner. This repository contains setup and usage documentation for the hosted MCP server.

Connect

  1. Open Cloud Wallet to set up your wallet and account policies.
  2. Add https://cloud.ekubo.org/mcp as a remote Streamable HTTP MCP server in your client.
  3. Follow the client's OAuth authorization link. The owner signs in, chooses the accounts and access to grant, and consents. Choose read access for account queries or write access when execution is needed. Write access includes read access at the same scope.
  4. Ask the agent to list the accounts available to the connection. It should call wallet_list and use the returned account identifiers for subsequent account requests.

Your client must support remote MCP connections and the server's OAuth flow. Producer MCP servers are separate connections; wallet_list_integrations lists supported producers and their connection URLs.

Capabilities

TaskTools
Discover accessible accounts and inspect their policieswallet_list, wallet_get_account
Read token balances and allowanceswallet_fetch_balances
Read contractswallet_batch_eth_call
Simulate a producer's execution planwallet_simulate_execution_plan
Request execution of a successful simulationwallet_send_execution_plan
Track a request through its final statuswallet_get_execution_status

Cloud Wallet has financial transaction capabilities. Requests are evaluated against account policies and service checks. Depending on those results, a request can execute automatically, be rejected, or wait for the owner's passkey approval.

Example requests

  • “List the accounts this connection can access.”
  • “Show the policy for this account.”
  • “Read this account's token balances.”

For an authorized transaction, connect the relevant producer MCP server, obtain its execution plan, and pass that plan unchanged to Cloud Wallet for simulation. A successful, sendable simulation provides a one-use simulation_id valid for 120 seconds. Send that ID with a fresh UUID idempotency key, then check request status until it is confirmed, failed, rejected, or cancelled. A pending_review result waits for the owner in the Cloud Wallet dashboard.

Use the server's live tool descriptions and instructions for the current arguments, permissions, limits, and recovery steps.

Documentation

Reviews

No reviews yet

Be the first to review this server!