Is the Laso Finance MCP server down?

mcp-registry/finance.laso/laso-finance · v1.0.0

up · requires sign-in
Last checked 2026-10-20 11:44 UTC · handshake 171ms

As of 2026-10-20 11:44 UTC, the Laso Finance MCP server is up (it requires sign-in) with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99%
checks observed
98
outages (90d)
1
tools
62

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

Install Laso Finance MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http laso-finance-mcp-server https://laso.finance/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "laso-finance-mcp-server": {
      "type": "http",
      "url": "https://laso.finance/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 4 warning(s) across 62 tool(s); ~14,321 tokens of tool definitions.
Scores higher than 10% of 15,401 MCP servers Glimind has audited.
Its tool list costs an agent ~14,321 tokens per session — more than 85% of servers.
67 → 74 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost75
Client compatibility70
Protocol100
Reliability75
Stability100

What to fix (6)

62 of 62 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: add_banking_destination, agent_wallet_transfer, announce_connection, cancel_intl_order, create_agent_api_key and 57 more

62 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

23 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: agent_wallet_transfer, cancel_intl_order, create_agent_api_key, create_agent_wallet, create_banking_account and 18 more

Reachable 99.0% of the time over the last 30 days; median recovery 8 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Requires authentication (Bearer); tool definitions could not be read anonymously.

If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.

Auto-fix: 53 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Ffinance.laso%2Flaso-finance/fixes

add_banking_destination 1 change
{
  "name": "add_banking_destination",
  "description": "Attach bank details to a recipient\n\nAttaches a bank account or crypto address to a recipient and returns the `destination_id` that `/send-bank-payment` pays out to.\n\nFree.",
  "inputSchema": {
    "type": "object",
    "required": [
      "recipientId",
      "destination"
    ],
    "properties": {
      "nickname": {
        "type": "string",
        "example": "Rent account",
        "description": "An optional label. The only field editable later, via `updateBankingDestination`."
      },
      "auth_token": {
        "type": "string",
        "description": "Laso credential. Only if the MCP connection has no Authorization header."
      },
      "destination": {
        "type": "object",
        "description": "The destination. For a US bank account: `destination_type: \"fiat_us\"` plus `aba_routing_number`, `account_number`, `account_type`, `account_holder_name`, and `bank_name`. Also supports `fiat_iban` and `crypto`."
      },
      "recipientId": {
        "type": "string",
        "description": "The recipient from `createBankingRecipient`."
      },
      "recipientAddress": {
        "type": "object",
        "description": "Sets the recipient's postal address before attaching the destination. Needed when the recipient was created name-only: bank destinations are rejected without one, so supplying it here avoids a dead end."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
agent_wallet_transfer 1 change
{
  "name": "agent_wallet_transfer",
  "description": "Transfer USDC out of your managed agent wallet to any Solana address. Use this to recover funds or move them to another wallet you control.",
  "inputSchema": {
    "type": "object",
    "required": [
      "destination_address",
      "amount"
    ],
    "properties": {
      "amount": {
        "type": "string",
        "description": "Decimal USDC amount to send, as a string (e.g. 25.50)."
      },
      "auth_token": {
        "type": "string",
        "description": "Laso credential. Only if the MCP connection has no Authorization header."
      },
      "destination_address": {
        "type": "string",
        "description": "Solana address to send the USDC to."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
cancel_intl_order 1 change
{
  "name": "cancel_intl_order",
  "description": "Cancel a queued international card order\n\nCancel a previously queued international non-reloadable card order, as long as it has not yet been fulfilled by an admin (`state=queued`). The charged amount is credited back to the account balance.",
  "inputSchema": {
    "type": "object",
    "required": [
      "card_id"
    ],
    "properties": {
      "card_id": {
        "type": "string",
        "description": "The card ID of the queued order to cancel (returned from `/order-intl-card`)"
      },
      "auth_token": {
        "type": "string",
        "description": "Laso credential. Only if the MCP connection has no Authorization header."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/finance.laso/laso-finance"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/finance.laso/laso-finance"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Ffinance.laso%2Flaso-finance.svg)](https://glimind.com/server/mcp-registry%2Ffinance.laso%2Flaso-finance?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Ffinance.laso%2Flaso-finance?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ffinance.laso%2Flaso-finance.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ffinance.laso%2Flaso-finance.svg
   :target: https://glimind.com/server/mcp-registry%2Ffinance.laso%2Flaso-finance?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3af82194f532fe36…, first seen 2026-10-17, included at leaf 6191 of 32,860. Version history · verify what your client received.

Tools (62)

Compare: most reliable finance servers · most reliable communication servers · most reliable security servers · most reliable data servers · most reliable payments servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Laso Finance MCP server down right now?

As of 2026-10-20 11:44 UTC, the Laso Finance MCP server is up (it requires sign-in) with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.

How many tools does Laso Finance MCP server provide?

Laso Finance MCP server advertises 62 tools, including add_banking_destination, agent_wallet_transfer, announce_connection, cancel_intl_order, create_agent_api_key.

How do I install Laso Finance MCP server?

Point your MCP client at this streamable-http endpoint: https://laso.finance/mcp

Is the Laso Finance MCP server safe to connect to an AI agent?

Glimind scanned all 62 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Laso Finance MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve