# uetr.ai - UETR and SWIFT Payment Tracking (remote · uetr.ai)

SWIFT payment tracking by UETR. Tools need OAuth/API key. API docs https://uetr.ai/docs/api

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `uetr.ai`: 87/100 (this document), [markdown](https://verifymcp.io/servers/ai-uetr-uetr-ai/uetr.md), [page](https://verifymcp.io/servers/ai-uetr-uetr-ai/uetr)

## Channel facts

- Endpoint: `https://uetr.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3-registry.2`

## 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-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4732 tokens (~139/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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.
  - Structured output schemas are declared (97% of tools); any adoption earns full credit.
- **Tool Safety**: 98/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 11 of 12 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 35 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 uetr.ai - UETR and SWIFT Payment Tracking MCP server?

uetr.ai - UETR and SWIFT Payment Tracking is a hosted endpoint at https://uetr.ai/mcp, 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 ai-uetr-uetr-ai 'https://uetr.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-uetr-uetr-ai": {
      "url": "https://uetr.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-uetr-uetr-ai": {
      "type": "http",
      "url": "https://uetr.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-uetr-uetr-ai]
url = "https://uetr.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-uetr-uetr-ai --url 'https://uetr.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-uetr-uetr-ai:
    url: "https://uetr.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-uetr-uetr-ai": {
      "Transport": "http",
      "Url": "https://uetr.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-uetr-uetr-ai -t streamable-http -u 'https://uetr.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-uetr-uetr-ai": {
      "type": "http",
      "url": "https://uetr.ai/mcp"
    }
  }
}
```

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-21 (score 87, +1)

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

### 2026-11-19 (score 86, +1)

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

### 2026-11-16 (score 85, +1)

- [security] Tool “list_team_members” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 1.0.2

### 2026-11-14 (score 84, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_plan_usage” rewrote its description, which is the text the model reads
- [security] Tool “recheck_transfer” rewrote its description, which is the text the model reads
- [functional] New tool “request_custom_quote”

### 2026-11-13 (score 83, 0)

- [security] Tool “export_transfers” rewrote its description, which is the text the model reads
- [security] Tool “get_transfer” rewrote its description, which is the text the model reads
- [security] Tool “list_transfers” rewrote its description, which is the text the model reads

### 2026-11-12 (score 83, +1)

- [security] Tool “add_transfer” rewrote its description, which is the text the model reads

### 2026-11-11 (score 82, 0)

- [security] Tool “export_transfers” rewrote its description, which is the text the model reads
- [security] Tool “get_transfer” rewrote its description, which is the text the model reads

### 2026-11-10 (score 82, 0)

- [security] Tool “list_team_members” rewrote its description, which is the text the model reads

## MCP tools (34)

### `add_transfer` (~316 tokens)

Add a transfer

Add a transfer to the account by its UETR, with the amount, currency and date it was sent. The account's plan decides how it is monitored, as for an add on the website. Adding a UETR the account already holds returns that transfer and uses no more of the plan, and keeps the amount, currency and date it holds: details_applied is false when they differ from the ones sent, and the account owner can correct them with update_transfer. An archived one is returned archived. Returns the transfer, the outcome and whether its details are the ones sent.

Input parameters:

- `amount` (object, required): The amount sent and its currency. The currency is a three-letter code in any letter case, one of USD, EUR, GBP, JPY, CHF, CAD, AUD, AED, BDT, BRL, CNY, HKD, IDR, ILS, INR, JOD, MAD, MXN, MYR, NZD, PH…
- `payment_date` (string, required): The date the payment was sent. It can be no earlier than 2000-01-01 and no later than the next calendar day in UTC.
- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`
- `details_applied` (boolean): Whether the transfer holds the amount, currency and payment date this request sent. false when the account already held it with other details: those details were kept, and the account owner can corre…
- `events`
- `free`
- `outcome` (string): created: a new transfer. existing: the account already held it. archived: the account holds it archived; restore it to resume monitoring.
- `transfer` (object)
- `waiting_at` (string|null): In the full view, the bank the payment is waiting at, when the reports name one; otherwise null.

### `archive_transfer` (~99 tokens)

Archive a transfer

Archive a transfer: its checks stop, and it and its timeline stay in the account. Archived transfers use no active transfer place. Restoring needs an active subscription and a free active transfer place, so on a free or lapsed account archiving ends the transfer's checks: it cannot be restored unless the account subscribes. Archiving an archived transfer changes nothing. Returns the transfer.

Input parameters:

- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`
- `events`
- `free`
- `transfer` (object)
- `waiting_at` (string|null)

### `change_webhook_endpoint_url` (~190 tokens)

Change a webhook endpoint's address

Send a webhook endpoint's events to a new HTTPS address, for example after the receiver moved. The endpoint keeps its id, events and signing secret, and returns to pending: until the account owner confirms the new address on the website it receives only test events, and the owner is normally notified by email. Deliveries still waiting for the old address are dropped, and a request still waiting on the old address is closed as withdrawn. If the owner declines, or nobody confirms within 7 days, the endpoint is removed. Sending the address an endpoint is already waiting on answers with its waiting request again. A change counts toward the hourly limit on adding endpoints. Only the account owner's API keys and connected apps can change webhooks.

Input parameters:

- `id` (string, required): The webhook endpoint's id.
- `url` (string, required): The full HTTPS address. It must use a domain name and the standard port.

Output parameters:

- `detail` (string): Plain English to pass on to the person behind the request.
- `endpoint` (object)
- `request` (object)
- `status` (string)

### `create_webhook_endpoint` (~148 tokens)

Add a webhook endpoint

Ask to send the account's transfer events to an HTTPS address: your own receiver, or a Slack or Microsoft Teams incoming webhook, which gets a readable message. The endpoint starts pending: it receives only test events, on a sample transfer, until the account owner confirms it on the website, and the owner is normally notified by email. The signing secret is returned once, here; deliveries carry Standard Webhooks headers signed with it. Only the account owner's API keys and connected apps can add endpoints.

Input parameters:

- `events` (array): The events to send. Defaults to all of them.
- `url` (string, required): The full HTTPS address. It must use a domain name and the standard port.

Output parameters:

- `detail` (string): Plain English to pass on to the person behind the request.
- `endpoint` (object)
- `request` (object)
- `signing_secret` (string): The secret that signs every delivery, starting whsec_. It is shown only now: store it in the receiver's secret settings.
- `status` (string)

### `decline_team_invitation` (~73 tokens)

Decline a team invitation

Decline an invitation addressed to the user behind this key or connection, using the token from their invitation link. Releases that pending seat without joining the team. It cannot decline another person's invitation or remove an active membership. Available on every plan.

Input parameters:

- `token` (string, required): The token from the recipient's invitation link.

Output parameters:

- `declined` (boolean)

### `delete_transfer` (~63 tokens)

Delete a transfer

Permanently delete a transfer from the account, archived or not, with its timeline. It cannot be undone; archiving keeps the transfer instead. Adding the UETR again later starts a new transfer.

Input parameters:

- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `deleted` (boolean)
- `uetr` (string): The UETR of the deleted transfer.

### `delete_webhook_endpoint` (~73 tokens)

Delete a webhook endpoint

Delete a webhook endpoint. Nothing more is sent to it, its delivery log is removed, and a confirmation still waiting for the account owner is closed as withdrawn. This cannot be undone. Only the account owner's API keys and connected apps can delete webhooks.

Input parameters:

- `id` (string, required): The webhook endpoint's id.

Output parameters:

- `deleted` (boolean)
- `id` (string)

### `export_transfers` (~210 tokens)

Export the account's transfers

Export every transfer in the account, archived ones included, with the bank reports its records hold: the same records the account's export download contains, named the API's way. A transfer in the free view exports with empty events even when banks have reported on it, so empty events there do not mean that no bank has reported; get_transfer gives the free view of those reports. A page holds up to 50 UETRs in UETR order, each exported once as one transfer however many times the account added it; pass next_cursor as cursor for the next page. An amount with a currency is in that currency's major units, not minor units: for example, 129600 USD means USD 129,600.00, not USD 1,296.00. Reading changes nothing.

Input parameters:

- `cursor` (string): The next_cursor of the previous page: the last UETR on that page. The page holds the UETRs after it, in UETR order.

Output parameters:

- `exported_at` (string)
- `next_cursor` (string|null): The last UETR on this page, to pass as cursor; null on the last page.
- `transfers` (array)

### `get_account` (~52 tokens)

Get the account

Get the account this API key or connected app acts on: its id, this user's role, the plan, and any scheduled deletion date. Check it to notice when that account changes or is ending. Reading changes nothing.

Output parameters:

- `account` (object)
- `credential` (object)

### `get_billing_link` (~60 tokens)

Get the billing page link

Get the address of the account's billing page on the website, where the account owner, signed in, manages the plan, payment details and invoices. Only the account owner can open it, so a teammate's key is refused. Reading changes nothing.

Output parameters:

- `url` (string): The billing page.

### `get_payment_record` (~107 tokens)

Get a payment record

Read a payment record from its link: the bank reports on a paid transfer, shared by its owner with whoever holds the link. Any key can read a record it has the link to, from any account. A link the owner replaced, or one that never existed, is not found. Reading changes nothing and is not counted as a visit to the record.

Input parameters:

- `record_token` (string, required): The token at the end of a payment record link (/p/...), or the whole link.

### `get_plan_usage` (~143 tokens)

Get plan usage

Get the account's plan and how many of its active transfers are in use. Free accounts have no active-transfer cap; lookup and request rate limits still apply. On a paid plan, a finished transfer keeps its place until it archives itself a week after its last check, and can be archived sooner to free the place. Archived transfers stay in the account and never count. On a custom package, also its terms: how many transfers were added in the current billing period against the package's volume and when it resets, how often each transfer is checked, for how many days, and how many on-demand re-checks the account may run a day. Reading changes nothing.

Output parameters:

- `active_transfers`: Null unless the account has an active paid plan. Null means this account is not measured against an active-transfer allowance; it does not mean zero transfers remain. Free accounts have no active-tra…
- `package`: Null unless the account has a custom package. Adds stop with monthly_limit_reached once added_this_period reaches included_transfers plus additional_transfers.
- `plan` (object)

### `get_share_link` (~92 tokens)

Get a transfer's share link

Get the link to a transfer's public status page, the page the website shares. Anyone with the link can open the page and, while the transfer is still being checked, sign up for its email alerts. The link stays the same for the life of the transfer, so share it only with people who should follow it. Reading changes nothing.

Input parameters:

- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `uetr` (string)
- `url` (string): The public status page.

### `get_transfer` (~345 tokens)

Get a transfer

Get one transfer in this account by its UETR, with every bank report in the full view, or the free tracker's view for a free transfer. When a bank last reported: in the free view, free.last_report_at is the newest bank report time, a time a bank gave (null when no report gives one), while free.last_update_at is only when the newest report was first received. free.delay counts whole days since the newest report, using the time its bank gave or, when the bank gave no time, when the report was first received, so it can be far shorter than the age of free.last_report_at. In the full view, each event's reported_at is the bank's own time. free.amount_bank_number and free.value_date_bank_number name which numbered bank (as in free.reports) reported the amount and the value date: they are bank numbers, not counts, and free.reporting_banks is the count. The number of people who follow the transfer's updates comes from get_watcher_count. The demo transfer 00000000-0000-4000-8000-000000000000 works for every key. Each hour (UTC) it is searching, with no bank reports, for its first 10 minutes, then gains a bank report every 10 minutes until it is credited at 50 minutes past the hour. An amount with a currency is in that currency's major units, not minor units: for example, 129600 USD means USD 129,600.00, not USD 1,296.00. Reading changes nothing.

Input parameters:

- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`: How many more corrections the account owner can make to the entered amount, currency and payment date now that a bank has reported. Null when no bank has reported, when the API key or connected app i…
- `events`: Every bank report, in the full view only, in the stage order of the transfer's timeline, earliest stage first: the last is the latest stage, which may have been received before an earlier stage's rep…
- `free`: The free tracker's view, in the free view only.
- `transfer` (object): The transfer.
- `waiting_at` (string|null): In the full view, the bank the payment is waiting at, when the reports name one; otherwise null.

### `get_watcher_count` (~100 tokens)

Count the people following a transfer

Count how many people follow a transfer's updates by email: those who receive its email alerts through its share link or payment record link, from sign-ups they confirmed and have not stopped, each address once. An archived transfer sends no alerts, so it counts none. It never returns their addresses, and alert sign-ups are made and stopped only by each person. Reading changes nothing.

Input parameters:

- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `uetr` (string)
- `watchers` (integer): How many people receive the alerts.

### `get_webhook_endpoint` (~60 tokens)

Get a webhook endpoint

Read one webhook endpoint: its masked address, status and events. The signing secret is never returned. Only the account owner's API keys and connected apps can read webhooks. Reading changes nothing.

Input parameters:

- `id` (string, required): The webhook endpoint's id.

Output parameters:

- `api_version` (string)
- `created_at` (string)
- `created_by` (string): website: added on the website. api: added by an API key or a connected app.
- `destination` (string): json: signed JSON. slack and teams: a readable message for a Slack or Microsoft Teams incoming webhook.
- `events` (array)
- `id` (string)
- `paused_at` (string|null)
- `status` (string): pending: waiting for the account owner to confirm it on the website; until then it receives test events only. active: receiving events. paused: deliveries stopped after sustained failures; a test eve…
- `url` (string): The address's host and a masked path. The full address is never shown.

### `invite_team_member` (~99 tokens)

Invite a teammate

Ask to invite someone to the team. The account owner must confirm the invitation on the website before anything happens: until then no invitation is sent and no seat is used. The owner sees the request on the website and is normally notified by email. Asking again for the same address returns the open request. Only the account owner's API keys and connected apps can ask, while the plan includes team seats.

Input parameters:

- `email` (string, required): The address to invite.

Output parameters:

- `detail` (string): Plain English to pass on to the person behind the request.
- `request` (object)
- `status` (string): Nothing has taken effect yet: the account owner must confirm the request.

### `list_pending_access` (~96 tokens)

List requests waiting for the owner

List the team invitations, payment record shares and webhook endpoints that API keys and connected apps asked for on this account, newest first, with whether the account owner confirmed, declined or has not answered yet, and whether a request expired or the API key or connected app that asked withdrew it. A confirmed record share carries the record link while it still works. Only the account owner's API keys and connected apps can list them. Reading changes nothing.

Output parameters:

- `requests` (array)

### `list_team_members` (~82 tokens)

List the team

Team invitations appear on this list after the account owner makes or confirms them. pending_owner_invitation_count counts invitations waiting for that confirmation. Use list_pending_access for request details. The team list also shows the owner, teammates and plan seats. Only the account owner's API keys and connected apps can list the team, while the plan includes team seats. Reading changes nothing.

Output parameters:

- `members` (array)
- `owner` (object)
- `pending_owner_invitation_count` (integer): Team invitation requests still waiting for the account owner to confirm. Zero when none wait.
- `seats` (object): Seats the plan includes and seats in use, the owner and pending invitations included.

### `list_transfers` (~212 tokens)

List transfers

List the transfers in this account with their current status, newest first (the dashboard's default order), one page at a time. Paid transfers come in the full view and the rest in the free view, as the dashboard shows them. Archived transfers are left out unless asked for. Pass next_cursor as cursor until it is null. The list holds no bank report times: last_checked_at is when the transfer was last checked, not when a bank last reported; get_transfer gives the newest bank report time. An amount with a currency is in that currency's major units, not minor units: for example, 129600 USD means USD 129,600.00, not USD 1,296.00. Reading changes nothing.

Input parameters:

- `archived` (string): exclude (default): active transfers. include: all. only: archived transfers.
- `cursor` (string): The next_cursor of the previous page.
- `limit` (integer): Transfers per page, 1 to 100. Default 50.

Output parameters:

- `next_cursor` (string|null): Pass as cursor for the next page; null on the last.
- `transfers` (array)

### `list_webhook_deliveries` (~83 tokens)

List a webhook endpoint's deliveries

List the most recent deliveries to a webhook endpoint, newest first, with each attempt count and the receiver's last HTTP status code. Deliveries are kept for 30 days and payloads are never returned. Only the account owner's API keys and connected apps can read webhooks. Reading changes nothing.

Input parameters:

- `id` (string, required): The webhook endpoint's id.

Output parameters:

- `deliveries` (array)

### `list_webhook_endpoints` (~61 tokens)

List webhook endpoints

List the account's webhook endpoints with their status and events, oldest first. Addresses show only their host and a masked path, and signing secrets are never returned. Only the account owner's API keys and connected apps can read webhooks. Reading changes nothing.

Output parameters:

- `endpoints` (array)

### `recheck_transfer` (~142 tokens)

Re-check a transfer now

Check the banks' trackers for this transfer now, then return it with any new reports. Available for transfers in the full view while monitoring runs and checks have not ended. A transfer can be re-checked once a minute and 20 times a day, and an account 20 times a minute and 500 times a day, counted together for the website and the API. On a custom package whose terms set a daily re-check allowance, the account's daily limit is that allowance (get_plan_usage package.rechecks_per_day). Only the account owner's API keys and connected apps can re-check.

Input parameters:

- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`
- `events`
- `free`
- `transfer` (object)
- `waiting_at` (string|null)

### `remove_team_member` (~98 tokens)

Remove a teammate

Remove a teammate from the account, or cancel a pending invitation, and free the seat. A removed teammate loses access to the account at once, and the API keys and connected apps they set up for it stop working. Transfers they added stay in the account. Only the account owner's API keys and connected apps can remove, while the plan includes team seats.

Input parameters:

- `member_id` (string, required): The teammate's seat id, from list_team_members.

Output parameters:

- `member_id` (string)
- `removed` (boolean)

### `rename_transfer` (~167 tokens)

Rename a transfer

Set or clear a transfer's label, at most 64 characters; an empty label clears it, as does one of only spaces or invisible characters. A label cannot contain tabs, line breaks or other control characters, or characters that override the direction of the text (U+202A to U+202E, U+2066 to U+2069). The direction marks U+200E, U+200F and U+061C are accepted, as right-to-left text uses them. A label can be set once the transfer has been found. Only the account owner's API keys and connected apps can rename a transfer. Returns the transfer.

Input parameters:

- `label` (required): The new label, or null to clear it.
- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`
- `events`
- `free`
- `transfer` (object)
- `waiting_at` (string|null)

### `request_custom_quote` (~193 tokens)

Request a Custom Monitor quote

Ask uetr.ai for a written Custom Monitor quote: a plan for more than 20 transfers at once, priced on request by monthly volume and check frequency, with webhooks, the REST API and MCP included. The quote goes by email to the address of the account that asks. We aim to reply by email within one business day with a written quote and a card payment link. An account can send 3 requests a day. Sending a request buys nothing and changes nothing in the account.

Input parameters:

- `check_frequency` (string): How often each transfer is checked: 5m (every 5 minutes, the standard), 1h, 12h (twice a day) or unsure.
- `monthly_transfers` (integer, required): How many transfers the account sends each month. There is no upper limit.
- `note` (string): Anything else the quote should consider, such as the systems to connect.

Output parameters:

- `message` (string): What happens next.
- `reply_to` (string): The email address the quote will be sent to.
- `requested` (boolean)

### `resend_team_invitation` (~83 tokens)

Resend a team invitation

Send a pending team invitation again when its delivery was not confirmed. An invitation already queued for delivery is refused, and invitations to one address are limited each hour. No seat changes. Only the account owner's API keys and connected apps can resend, while the plan includes team seats.

Input parameters:

- `member_id` (string, required): The teammate's seat id, from list_team_members.

Output parameters:

- `delivery` (string): sent: the invitation is queued for delivery. unverified: delivery could not be confirmed, so the invitation may not arrive; resend_team_invitation can try again.
- `email` (string)
- `member_id` (string)

### `restore_transfer` (~117 tokens)

Restore an archived transfer

Restore an archived transfer so its monitoring resumes. Restoring needs an active subscription and a free active transfer place. A restored transfer is monitored until the plan's current period ends: the end of the subscription's billing period, the end date of a courtesy grant, or 30 days from the restore for a courtesy grant with no end date. Its checks run every 5 minutes, which set_check_frequency can change. Restoring an active transfer changes nothing. Returns the transfer.

Input parameters:

- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`
- `events`
- `free`
- `transfer` (object)
- `waiting_at` (string|null)

### `rotate_webhook_secret` (~143 tokens)

Rotate a webhook signing secret

Replace a webhook endpoint's signing secret, for example after it was exposed. The new secret is returned once, here. For the next 24 hours every delivery carries two signatures, one with the new secret and one with the previous secret, so the receiver keeps accepting requests while it is updated; after that only the new secret signs. Rotating again within those 24 hours ends the oldest secret at once: only the secret in use at that moment keeps signing beside the new one. The address, events and status do not change. Only the account owner's API keys and connected apps can rotate a secret.

Input parameters:

- `id` (string, required): The webhook endpoint's id.

Output parameters:

- `endpoint` (object)
- `previous_secret_expires_at` (string): When the previous secret stops signing deliveries: 24 hours after the rotation.
- `signing_secret` (string): The new secret that signs every delivery, starting whsec_. It is shown only now: store it in the receiver's secret settings.

### `send_webhook_test` (~84 tokens)

Send a test event

Queue one test event to a webhook endpoint, about a sample transfer and never one of the account's own. It is sent within about a minute; read the endpoint's deliveries to see the receiver's answer. Pending endpoints can receive test events. Only the account owner's API keys and connected apps can send tests.

Input parameters:

- `id` (string, required): The webhook endpoint's id.

Output parameters:

- `delivery` (object)

### `set_check_frequency` (~148 tokens)

Set a transfer's check frequency

Set how often this transfer's own checks run, in minutes: one of 5, 15, 30, 60, 180, 360, 720, 1440. Only a paid transfer whose monitoring runs and whose checks have not ended has a frequency to set; a free, finished or lapsed transfer keeps its schedule. Only the account owner's API keys and connected apps can change it. Returns the transfer.

Input parameters:

- `minutes` (integer, required): Minutes between checks: one of 5, 15, 30, 60, 180, 360, 720, 1440.
- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`
- `events`
- `free`
- `transfer` (object)
- `waiting_at` (string|null)

### `share_payment_record` (~178 tokens)

Share a payment record

Ask for the payment record link of a paid transfer, to share its bank reports. The account owner must confirm the request on the website before the link is shared: until then the caller does not receive it. The owner sees the request on the website and is normally notified by email. Once confirmed, list_pending_access returns the link. Asking again for the same transfer with the same settings returns the open request; with different settings, the new request replaces it. Only the account owner's API keys and connected apps can ask.

Input parameters:

- `show_commentary` (boolean): Show uetr.ai's plain-language explanations on the record. Leave out to keep the current setting.
- `show_fees` (boolean): Show bank fees on the record. Leave out to keep the current setting.
- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `detail` (string): Plain English to pass on to the person behind the request.
- `request` (object)
- `status` (string): Nothing has taken effect yet: the account owner must confirm the request.

### `update_transfer` (~385 tokens)

Correct a transfer's details

Corrects the amount, currency or payment date entered for a transfer. Bank-reported figures never change. After a bank has reported, the owner can make up to 3 corrections. The owner's corrections on the website count toward the same limit. Give all three details as they should stand; a correction replaces them together, as the website's form does. After a bank has reported, sending the details every copy of this transfer in the account already holds changes nothing and uses no correction; if an older copy holds other details, the save aligns it and counts as one correction. Before a report, every save checks the transfer again. The UETR cannot be changed: it identifies the payment. A correction is refused once the transfer is archived, or when its checks ended before any bank reported on it. Only the account owner's API keys and connected apps can correct details. Returns the transfer, the outcome and the corrections left.

Input parameters:

- `amount` (object, required): The amount sent and its currency. The currency is a three-letter code in any letter case, one of USD, EUR, GBP, JPY, CHF, CAD, AUD, AED, BDT, BRL, CNY, HKD, IDR, ILS, INR, JOD, MAD, MXN, MYR, NZD, PH…
- `payment_date` (string, required): The date the payment was sent. A changed date can be no earlier than 2000-01-01 and no later than the next calendar day in UTC.
- `uetr` (string, required): The transfer's UETR.

Output parameters:

- `corrections_remaining`
- `events`
- `free`
- `outcome` (string): requeued: no bank had reported yet, so the next check uses the corrected details and no correction was used. corrected: a bank had reported, so the entered details were corrected and one correction w…
- `transfer` (object)
- `waiting_at` (string|null): In the full view, the bank the payment is waiting at, when the reports name one; otherwise null.

### `update_webhook_endpoint` (~137 tokens)

Change a webhook endpoint's events

Choose which events a webhook endpoint receives. The address is changed with change_webhook_endpoint_url instead, and the account owner confirms the new one. Only the account owner's API keys and connected apps can change webhooks.

Input parameters:

- `events` (array, required): status_changed: a transfer's status changed. final_state: a transfer reached a final state, such as credited or returned. checks_ended: automatic checks on a transfer ended before a final state, incl…
- `id` (string, required): The webhook endpoint's id.

Output parameters:

- `api_version` (string)
- `created_at` (string)
- `created_by` (string)
- `destination` (string)
- `events` (array)
- `id` (string)
- `paused_at` (string|null)
- `status` (string)
- `url` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 87
- 2026-11-20: 86
- 2026-11-19: 86
- 2026-11-18: 85
- 2026-11-17: 85
- 2026-11-16: 85
- 2026-11-15: 84
- 2026-11-14: 84
- 2026-11-13: 83
- 2026-11-12: 83
- 2026-11-11: 82
- 2026-11-10: 82
- 2026-11-09: 82
- 2026-11-08: 81
- 2026-11-07: 81
- 2026-11-06: 80
- 2026-11-05: 80

## Common questions

### What is the uetr.ai - UETR and SWIFT Payment Tracking MCP server?

uetr.ai - UETR and SWIFT Payment Tracking is an MCP server listed in the public MCP registry as ai.uetr/uetr.ai. SWIFT payment tracking by UETR. Tools need OAuth/API key. API docs https://uetr.ai/docs/api. This page covers its hosted endpoint (https://uetr.ai/mcp).

### Is the uetr.ai - UETR and SWIFT Payment Tracking MCP server safe to use?

uetr.ai - UETR and SWIFT Payment Tracking scores 87 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 uetr.ai - UETR and SWIFT Payment Tracking MCP server expose?

uetr.ai - UETR and SWIFT Payment Tracking exposes 34 tools: add_transfer, archive_transfer, change_webhook_endpoint_url, create_webhook_endpoint, decline_team_invitation, and 29 more. Their descriptions and schemas cost roughly 4,639 tokens of context every time the server is loaded.

### Does the uetr.ai - UETR and SWIFT Payment Tracking MCP server require authentication?

Yes. uetr.ai - UETR and SWIFT Payment Tracking asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the uetr.ai - UETR and SWIFT Payment Tracking MCP server still maintained?

uetr.ai - UETR and SWIFT Payment Tracking is still listed as active in the MCP registry. We last reached this channel on 21 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 uetr.ai - UETR and SWIFT Payment Tracking MCP server?

VerifyMCP ran 13 checks on uetr.ai - UETR and SWIFT Payment Tracking, 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://uetr.ai/mcp
- Website: https://uetr.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-uetr-uetr-ai/uetr.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-uetr-uetr-ai/uetr/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-uetr-uetr-ai/uetr.json
- HTML version of this page: https://verifymcp.io/servers/ai-uetr-uetr-ai/uetr
