# Morse (remote · mcp.morsemoney.com)

Exchange rates, where Morse can send money, and indicative transfer quotes. No login needed.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `mcp.morsemoney.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-morsemoney-morse/v1.md), [page](https://verifymcp.io/servers/com-morsemoney-morse/v1)

## Channel facts

- Endpoint: `https://mcp.morsemoney.com/v1`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 590 tokens (~196/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "list_send_destinations" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Morse MCP server?

Morse is a hosted endpoint at https://mcp.morsemoney.com/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-morsemoney-morse 'https://mcp.morsemoney.com/v1'
```

### Cursor

```json
{
  "mcpServers": {
    "com-morsemoney-morse": {
      "url": "https://mcp.morsemoney.com/v1"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-morsemoney-morse": {
      "type": "http",
      "url": "https://mcp.morsemoney.com/v1"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-morsemoney-morse]
url = "https://mcp.morsemoney.com/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-morsemoney-morse": {
      "type": "remote",
      "url": "https://mcp.morsemoney.com/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-morsemoney-morse --url 'https://mcp.morsemoney.com/v1' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-morsemoney-morse:
    url: "https://mcp.morsemoney.com/v1"
```

### Netclaw

```json
{
  "McpServers": {
    "com-morsemoney-morse": {
      "Transport": "http",
      "Url": "https://mcp.morsemoney.com/v1"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-morsemoney-morse -t streamable-http -u 'https://mcp.morsemoney.com/v1'
```

### Other

```json
{
  "mcpServers": {
    "com-morsemoney-morse": {
      "type": "http",
      "url": "https://mcp.morsemoney.com/v1"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 70)

First indexed and scored.

## MCP tools (3)

### `get_exchange_rate` (~157 tokens)

Returns the current mid-market exchange rate between two currencies as the number of units of to_currency per one unit of from_currency, with the time it was read. Use it to answer how much one currency is worth in another. It does not say whether Morse can send money in either currency; use list_send_destinations for that. The rate is indicative; show get_started_url as the way to continue in the Morse app, where the rate applied to a transfer is shown before the user confirms.

Input parameters:

- `from_currency` (string, required): ISO 4217 code of the currency to convert from, e.g. USD.
- `to_currency` (string, required): ISO 4217 code of the currency to convert to, e.g. MXN.

### `list_send_destinations` (~149 tokens)

Returns the countries, currencies and payment rails a person living in from_country can send money to with Morse when paying someone else's bank account, with the typical delivery time for each. Use it to answer whether Morse can send from one country to another. An empty destinations list means sending to other people's bank accounts is not offered from that country. When the result includes get_started_url, show it to the user as the way to continue in the Morse app.

Input parameters:

- `from_country` (string, required): ISO 3166-1 alpha-2 code of the country the sender lives in, e.g. US. If the user has not said where they live, ask them before quoting; do not assume.

### `quote_send` (~284 tokens)

Returns an indicative quote for sending money with Morse from a person living in from_country to someone else's bank account in to_country: the amount sent, the fee, the mid-market exchange rate and what the recipient gets. The result includes the total cost of the transfer and the typical delivery time. Use it to answer how much a transfer costs or how much will arrive. Use list_send_destinations first to check the destination is offered. Present the figures as indicative and tell the user to check the final rate and fees in the Morse app, using get_started_url.

Input parameters:

- `amount` (number, required): Amount to send, in from_currency, e.g. 250 or 99.50.
- `from_country` (string, required): ISO 3166-1 alpha-2 code of the country the sender lives in, e.g. US. If the user has not said where they live, ask them before quoting; do not assume.
- `from_currency` (string): ISO 4217 code of the currency the sender pays in. Defaults to the currency of from_country.
- `to_country` (string, required): ISO 3166-1 alpha-2 code of the country of the recipient's bank account, e.g. MX.
- `to_currency` (string): ISO 4217 code of the currency the recipient receives. Defaults to the currency Morse pays out in to_country.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-morsemoney-morse/v1#diagnostics

## Score history

- 2026-11-06: 74
- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70

## Common questions

### What is the Morse MCP server?

Morse is an MCP server listed in the public MCP registry as com.morsemoney/morse. Exchange rates, where Morse can send money, and indicative transfer quotes. No login needed. This page covers its hosted endpoint (https://mcp.morsemoney.com/v1).

### Is the Morse MCP server safe to use?

Morse scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Morse MCP server expose?

Morse exposes 3 tools: get_exchange_rate, list_send_destinations, quote_send. Their descriptions and schemas cost roughly 590 tokens of context every time the server is loaded.

### Does the Morse MCP server require authentication?

No. We connected to Morse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Morse MCP server still maintained?

Morse is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Morse MCP server?

VerifyMCP ran 13 checks on Morse, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.morsemoney.com/v1
- Website: https://mcp.morsemoney.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-morsemoney-morse/v1.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-morsemoney-morse/v1/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-morsemoney-morse/v1.json
- HTML version of this page: https://verifymcp.io/servers/com-morsemoney-morse/v1