Cloud Wallet by Ekubo

io.github.EkuboProtocolPublished by GitHub account EkuboProtocolv1.0.0Updated Nov 4, 2026

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

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote EVM wallet server that lets an assistant read wallet state, simulate transactions, and execute them under user-defined authorization policies.

What you can do
  • Read EVM wallet information such as balances and account state
  • Simulate transactions before they are submitted
  • Execute transactions on EVM chains, subject to authorization policies the user defines
  • Operate through a hosted endpoint with OAuth sign-in rather than a local install
When to use it
Useful when an assistant should inspect an EVM wallet, preview the effect of a transaction, and then carry it out within limits the user has set, without running wallet software locally.
Requirements
A remote MCP endpoint at cloud.ekubo.org over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared, and no local package is needed.
Before you install
The server can execute on-chain transactions, which move funds and are irreversible; scope the authorization policies narrowly. Access is granted through OAuth to a hosted wallet service, so the provider sees wallet activity. No tool list is published, so confirm exactly which chains and actions are exposed before relying on it.

Installation

In SourceWeft

  1. Open Cloud Wallet by Ekubo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.EkuboProtocol%2Fcloud-wallet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cloud-wallet-by-ekubo": {
      "type": "http",
      "url": "https://cloud.ekubo.org/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.