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
Available components
Last scanned (22 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 21 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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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
- Structured output schemas are declared (97% of tools); any adoption earns full credit.Pass
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Partial
- An AI judge read all 35 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.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 16 Nov 26 +1
- Tool “list_team_members” rewrote its description, which is the text the model reads security
- Server version: 1.0.0 → 1.0.2 functional
- 14 Nov 26 +1
- 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 security
- New tool “request_custom_quote” functional
- 13 Nov 26 0
- 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 security
- 12 Nov 26 +1
- Tool “add_transfer” rewrote its description, which is the text the model reads security
- 11 Nov 26 0
- 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
- 10 Nov 26 0
- Tool “list_team_members” rewrote its description, which is the text the model reads security
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 21 Nov 2026 · Probed https://uetr.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=uetr.ai | CN=WE1,O=Google Trust Services,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | fd424027adcaa50613886c8dc45fa3d7 |
| SANs: uetr.ai | ||||||
| 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 uetr.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| uetr.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer scope="read write", resource_metadata="https://uetr.ai/.well-known/oauth-protected-resource/mcp"
Bearer scope="read write", resource_metadata="https://uetr.ai/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://uetr.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://uetr.ai/mcp |
| Authorisation server | https://auth.uetr.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://uetr.ai/mcp | Verified | 200 | |
| http (plaintext) | http://uetr.ai/mcp | HTTPS enforced | 301 | https://uetr.ai/mcp |
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 →
add_transfer Add a transfer ~316
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | object | yes | 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 | yes | 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 | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | – |
| details_applied | boolean | yes | 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 | – | yes | – |
| free | – | yes | – |
| outcome | string | yes | created: a new transfer. existing: the account already held it. archived: the account holds it archived; restore it to resume monitoring. |
| transfer | object | yes | – |
| waiting_at | string|null | yes | In the full view, the bank the payment is waiting at, when the reports name one; otherwise null. |
No examples provided.
archive_transfer Archive a transfer ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | – |
| events | – | yes | – |
| free | – | yes | – |
| transfer | object | yes | – |
| waiting_at | string|null | yes | – |
No examples provided.
change_webhook_endpoint_url Change a webhook endpoint's address ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The webhook endpoint's id. |
| url | string | yes | The full HTTPS address. It must use a domain name and the standard port. |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | Plain English to pass on to the person behind the request. |
| endpoint | object | yes | – |
| request | object | yes | – |
| status | string | yes | – |
No examples provided.
create_webhook_endpoint Add a webhook endpoint ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | The events to send. Defaults to all of them. |
| url | string | yes | The full HTTPS address. It must use a domain name and the standard port. |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | Plain English to pass on to the person behind the request. |
| endpoint | object | yes | – |
| request | object | yes | – |
| signing_secret | string | yes | The secret that signs every delivery, starting whsec_. It is shown only now: store it in the receiver's secret settings. |
| status | string | yes | – |
No examples provided.
decline_team_invitation Decline a team invitation ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The token from the recipient's invitation link. |
| Name | Type | Req | Description |
|---|---|---|---|
| declined | boolean | yes | – |
No examples provided.
delete_transfer Delete a transfer ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| uetr | string | yes | The UETR of the deleted transfer. |
No examples provided.
delete_webhook_endpoint Delete a webhook endpoint ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The webhook endpoint's id. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| id | string | yes | – |
No examples provided.
export_transfers Export the account's transfers ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| exported_at | string | yes | – |
| next_cursor | string|null | yes | The last UETR on this page, to pass as cursor; null on the last page. |
| transfers | array | yes | – |
No examples provided.
get_account Get the account ~52
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| credential | object | yes | – |
No examples provided.
get_billing_link Get the billing page link ~60
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The billing page. |
No examples provided.
get_payment_record Get a payment record ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record_token | string | yes | The token at the end of a payment record link (/p/...), or the whole link. |
No output schema declared.
No examples provided.
get_plan_usage Get plan usage ~143
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| active_transfers | – | yes | 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 | – | yes | 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 | yes | – |
No examples provided.
get_share_link Get a transfer's share link ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | – |
| url | string | yes | The public status page. |
No examples provided.
get_transfer Get a transfer ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | 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 | – | yes | 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 | – | yes | The free tracker's view, in the free view only. |
| transfer | object | yes | The transfer. |
| waiting_at | string|null | yes | In the full view, the bank the payment is waiting at, when the reports name one; otherwise null. |
No examples provided.
get_watcher_count Count the people following a transfer ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | – |
| watchers | integer | yes | How many people receive the alerts. |
No examples provided.
get_webhook_endpoint Get a webhook endpoint ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The webhook endpoint's id. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| created_at | string | yes | – |
| created_by | string | yes | website: added on the website. api: added by an API key or a connected app. |
| destination | string | yes | json: signed JSON. slack and teams: a readable message for a Slack or Microsoft Teams incoming webhook. |
| events | array | yes | – |
| id | string | yes | – |
| paused_at | string|null | yes | – |
| status | string | yes | 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 | yes | The address's host and a masked path. The full address is never shown. |
No examples provided.
invite_team_member Invite a teammate ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The address to invite. |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | Plain English to pass on to the person behind the request. |
| request | object | yes | – |
| status | string | yes | Nothing has taken effect yet: the account owner must confirm the request. |
No examples provided.
list_pending_access List requests waiting for the owner ~96
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| requests | array | yes | – |
No examples provided.
list_team_members List the team ~82
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| members | array | yes | – |
| owner | object | yes | – |
| pending_owner_invitation_count | integer | yes | Team invitation requests still waiting for the account owner to confirm. Zero when none wait. |
| seats | object | yes | Seats the plan includes and seats in use, the owner and pending invitations included. |
No examples provided.
list_transfers List transfers ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| next_cursor | string|null | yes | Pass as cursor for the next page; null on the last. |
| transfers | array | yes | – |
No examples provided.
list_webhook_deliveries List a webhook endpoint's deliveries ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The webhook endpoint's id. |
| Name | Type | Req | Description |
|---|---|---|---|
| deliveries | array | yes | – |
No examples provided.
list_webhook_endpoints List webhook endpoints ~61
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | – |
No examples provided.
recheck_transfer Re-check a transfer now ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | – |
| events | – | yes | – |
| free | – | yes | – |
| transfer | object | yes | – |
| waiting_at | string|null | yes | – |
No examples provided.
remove_team_member Remove a teammate ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The teammate's seat id, from list_team_members. |
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | – |
| removed | boolean | yes | – |
No examples provided.
rename_transfer Rename a transfer ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | – | yes | The new label, or null to clear it. |
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | – |
| events | – | yes | – |
| free | – | yes | – |
| transfer | object | yes | – |
| waiting_at | string|null | yes | – |
No examples provided.
request_custom_quote Request a Custom Monitor quote ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What happens next. |
| reply_to | string | yes | The email address the quote will be sent to. |
| requested | boolean | yes | – |
No examples provided.
resend_team_invitation Resend a team invitation ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The teammate's seat id, from list_team_members. |
| Name | Type | Req | Description |
|---|---|---|---|
| delivery | string | yes | 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. |
| string | yes | – | |
| member_id | string | yes | – |
No examples provided.
restore_transfer Restore an archived transfer ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | – |
| events | – | yes | – |
| free | – | yes | – |
| transfer | object | yes | – |
| waiting_at | string|null | yes | – |
No examples provided.
rotate_webhook_secret Rotate a webhook signing secret ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The webhook endpoint's id. |
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | object | yes | – |
| previous_secret_expires_at | string | yes | When the previous secret stops signing deliveries: 24 hours after the rotation. |
| signing_secret | string | yes | The new secret that signs every delivery, starting whsec_. It is shown only now: store it in the receiver's secret settings. |
No examples provided.
send_webhook_test Send a test event ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The webhook endpoint's id. |
| Name | Type | Req | Description |
|---|---|---|---|
| delivery | object | yes | – |
No examples provided.
set_check_frequency Set a transfer's check frequency ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | yes | Minutes between checks: one of 5, 15, 30, 60, 180, 360, 720, 1440. |
| uetr | string | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | – |
| events | – | yes | – |
| free | – | yes | – |
| transfer | object | yes | – |
| waiting_at | string|null | yes | – |
No examples provided.
share_payment_record Share a payment record ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | Plain English to pass on to the person behind the request. |
| request | object | yes | – |
| status | string | yes | Nothing has taken effect yet: the account owner must confirm the request. |
No examples provided.
update_transfer Correct a transfer's details ~385
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | object | yes | 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 | yes | 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 | yes | The transfer's UETR. |
| Name | Type | Req | Description |
|---|---|---|---|
| corrections_remaining | – | yes | – |
| events | – | yes | – |
| free | – | yes | – |
| outcome | string | yes | 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 | yes | – |
| waiting_at | string|null | yes | In the full view, the bank the payment is waiting at, when the reports name one; otherwise null. |
No examples provided.
update_webhook_endpoint Change a webhook endpoint's events ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | 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 | yes | The webhook endpoint's id. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | string | yes | – |
| created_at | string | yes | – |
| created_by | string | yes | – |
| destination | string | yes | – |
| events | array | yes | – |
| id | string | yes | – |
| paused_at | string|null | yes | – |
| status | string | yes | – |
| url | string | yes | – |
No examples provided.
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.
remote · uetr.ai
claude mcp add --transport http ai-uetr-uetr-ai 'https://uetr.ai/mcp'
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.