Morse
REMOTE · MCP.MORSEMONEY.COM
Exchange rates, where Morse can send money, and indicative transfer quotes. No login needed.
Available components
Last scanned (6 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 30 Oct 26 +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.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.morsemoney.com/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=morsemoney.com | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b9204fb6322bcc7a1385afe93386fd0d |
| SANs: morsemoney.com, *.morsemoney.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.morsemoney.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| morsemoney.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.morsemoney.com/v1 | Verified | 200 | |
| http (plaintext) | http://mcp.morsemoney.com/v1 | HTTPS enforced | 301 | https://mcp.morsemoney.com/v1 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_exchange_rate ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_currency | string | yes | ISO 4217 code of the currency to convert from, e.g. USD. |
| to_currency | string | yes | ISO 4217 code of the currency to convert to, e.g. MXN. |
No output schema declared.
No examples provided.
list_send_destinations ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_country | string | yes | 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. |
No output schema declared.
No examples provided.
quote_send ~284
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to send, in from_currency, e.g. 250 or 99.50. |
| from_country | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · mcp.morsemoney.com
claude mcp add --transport http com-morsemoney-morse 'https://mcp.morsemoney.com/v1'
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 73 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 5 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.