QAmcp

Copied. Paste it into Claude Code, Cursor or Codex:Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.

Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions

NewYour score can change any day. QAmcp Monitor keeps testing your server and emails you when it breaks. Free for 1 server.See what Monitor does →

Directory / uetr.ai - SWIFT Payment Tracking

uetr.ai - SWIFT Payment Tracking

Q: Is uetr.ai - SWIFT Payment Tracking MCP server safe?

QAmcp's test on 5 Nov 2026: None of the hidden-instruction wordings we know were found in its 33 tool descriptions. Its error messages showed no secrets or internal details. 14 of its 33 tools are labeled read-only; the others may change or send things. Overall it scored 91/100 on 5 Nov 2026. A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

by uetr.ai · https://uetr.ai/mcp

Track SWIFT payments by UETR, read bank-reported status, and manage transfer monitoring.

33 tools✓ no account neededPricing: on their site

See pricing →Visit website

91 /100

PASS · WITH NOTES

Partial: 9 of 11 checks · 5 Nov 2026

Test it now for current results

At a glance

Runs where: On their server. What you send to it goes to them.
What you need: Nothing: it answered without a login
Tools: 33 tools
Its own safety labels: 14 read-only, 15 labeled as deleting or destroying, 4 labeled as changing things
Memory it takes: About 7,400 tokens of your AI's memory, just for its tool descriptions
Tools that look alike: 1 pair of tools with nearly the same description, so the AI may pick the wrong one

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 5 Nov 2026.

Is uetr.ai - SWIFT Payment Tracking MCP server safe?

None of the hidden-instruction wordings we know were found in its 33 tool descriptions.
Its error messages showed no secrets or internal details.
14 of its 33 tools are labeled read-only; the others may change or send things.
Overall it scored 91/100 on 5 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

Its source code and packages.
What a tool quietly does behind the scenes, such as writing a file or calling another service.
Instructions hidden inside live tool answers. We only look for those in tool descriptions.
Hidden instructions worded in a way our list doesn't know yet.
Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.

What it can do

33 tools, in the server's own words.

add_transfer

Add a transfer to the account by its UETR, with the amount, currency and date it was sent.

archive_transfer

Archive a transfer: its checks stop, and it and its timeline stay in the account.

change_webhook_endpoint_url

Send a webhook endpoint's events to a new HTTPS address, for example after the receiver moved.

create_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.

decline_team_invitation

Decline an invitation addressed to the user behind this key or connection, using the token from their invitation link.

delete_transfer

Permanently delete a transfer from the account, archived or not, with its timeline.

delete_webhook_endpoint

Delete a webhook endpoint.

export_transfersread-only

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, …

get_accountread-only

Get the account this API key or connected app acts on: its id, this user's role, the plan, and any scheduled deletion date.

get_billing_linkread-only

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.

get_payment_recordread-only

Read a payment record from its link: the bank reports on a paid transfer, shared by its owner with whoever holds the link.

get_plan_usageread-only

Get the account's plan and how many of its active transfers are in use.

get_share_linkread-only

Get the link to a transfer's public status page, the page the website shares.

get_transferread-only

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.

get_watcher_countread-only

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 the…

get_webhook_endpointread-only

Read one webhook endpoint: its masked address, status and events.

invite_team_member

Ask to invite someone to the team.

list_pending_accessread-only

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 t…

list_team_membersread-only

List the people who share this account: the owner, each teammate and each pending invitation, with the seats the plan includes.

list_transfersread-only

List the transfers in this account with their current status, newest first (the dashboard's default order), one page at a time.

list_webhook_deliveriesread-only

List the most recent deliveries to a webhook endpoint, newest first, with each attempt count and the receiver's last HTTP status code.

list_webhook_endpointsread-only

List the account's webhook endpoints with their status and events, oldest first.

recheck_transfer

Check the banks' trackers for this transfer now, then return it with any new reports.

remove_team_member

Remove a teammate from the account, or cancel a pending invitation, and free the seat.

and 9 more

Test results

Safe mode: only tools labeled read-only were run. How the test works

!
Every tool is described
1 warning
- !get_webhook_endpoint and list_webhook_endpoints have nearly the same description (69% of their words are shared; the only difference: "address" vs "list", "their", "oldest"), so an AI may not know which to pick
note
!
Follows MCP best practices (not scored yet)
1 tip (not scored)
- !The tool list is about 189 KB (roughly 47k tokens). AI apps send it with every message, so it takes that much of the AI's memory before any work starts.
note
✓
ConnectsConnected in 1.3 s
pass
✓
Ready for the newest MCP versionUses the latest MCP version (2026-07-28)
pass
✓
Lists its toolsFound 33 tools
pass
✓
Tools are labeled safe or dangerousEvery tool has a safety label
pass
✓
No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
pass
✓
Fast enough
All good
- ✓Connecting took 1.3 s
- ✓Listing tools took 838 ms
pass
✓
No secrets leakedChecked 28 error messages: no secrets or internal details
pass
–
Tools work with good inputs
Not tested
- –export_transfers: Needs you to sign in, so it was not tested (not counted against the server)
- –get_account: Needs you to sign in, so it was not tested (not counted against the server)
- –get_billing_link: Needs you to sign in, so it was not tested (not counted against the server)
- –get_payment_record: Needs you to sign in, so it was not tested (not counted against the server)
- –get_plan_usage: Needs you to sign in, so it was not tested (not counted against the server)
- –get_share_link: Needs you to sign in, so it was not tested (not counted against the server)
- –get_transfer: Needs you to sign in, so it was not tested (not counted against the server)
- –get_watcher_count: Needs you to sign in, so it was not tested (not counted against the server)
- and 25 more
not tested
–
Bad inputs give a clean error
Not tested
- –export_transfers: Needs you to sign in, so bad inputs were not tested
- –get_payment_record: Needs you to sign in, so bad inputs were not tested
- –get_share_link: Needs you to sign in, so bad inputs were not tested
- –get_transfer: Needs you to sign in, so bad inputs were not tested
- –get_watcher_count: Needs you to sign in, so bad inputs were not tested
- –get_webhook_endpoint: Needs you to sign in, so bad inputs were not tested
- –list_transfers: Needs you to sign in, so bad inputs were not tested
- –list_webhook_deliveries: Needs you to sign in, so bad inputs were not tested
not tested
–
Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)
not tested

Test it yourself

Free and open source. Same checks, same score.

npx qamcp-cli https://uetr.ai/mcp

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

[![QAmcp score](https://qamcp.dev/s/ai-uetr-uetr-ai.svg)](https://qamcp.dev/s/ai-uetr-uetr-ai.html)

Score over time

5 Nov 202691

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use uetr.ai - SWIFT Payment Tracking, signed in with GitHub, one per person. Reviews never change the score.

Is this your server? Get an alert the moment it breaks.

QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.

Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works