Laso Finance

finance.lasoPublished by laso.financeOfficial publisherv1.0.0Updated Oct 24, 2026

Spend USDC in the real world: prepaid cards, gift cards, push-to-card, and bank payouts.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Lets an assistant spend USDC on real-world payments such as prepaid cards, gift cards, push-to-card transfers and bank payouts through Laso Finance.

What you can do
Laso Finance is a remote MCP endpoint for moving USDC into real-world spending. Based on the description, it covers prepaid cards, gift cards, push-to-card transfers and bank payouts. The manifest lists no tools, so the exact operations are not documented here; only get_version and search_docs are named as working without authentication.
When to use it
Consider it when you want an assistant to help with real-world payments funded by USDC, such as buying cards or sending funds to a card or bank account. It is not a general finance or market-data tool.
Requirements
A remote endpoint at laso.finance over streamable HTTP; no local package is needed. OAuth authentication is required, using an Authorization header carrying either a Laso API key or an id_token. get_version and search_docs reportedly work without credentials.
Before you install
This server moves money: it can spend USDC and trigger card and bank payouts, so actions may be irreversible and incur fees. The Authorization header carries a secret API key or token; keep it private. Confirm amounts and recipients before letting an assistant act.

Installation

In SourceWeft

  1. Open Laso Finance 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/finance.laso%2Flaso-finance/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": {
    "laso-finance": {
      "type": "http",
      "url": "https://laso.finance/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.0LatestSep 26, 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.