uetr.ai - UETR and SWIFT Payment Tracking
https://uetr.ai/mcp
● healthy
Remote MCP server for UETR tracking and SWIFT payment tracking. Read bank-reported transfer status and manage monitoring within your plan and team permissions. Connect with OAuth or a uetr.ai API key.
- uetr-tracking
- swift-payment-tracking
- payment-monitoring
Transport
streamable-http
Auth
oauth
Cost
—
Protocol revision
2025-11-25
negotiated, not declared
MCP readiness
A · 93/100
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 71.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1819 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 8/8 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 33 tool(s) with descriptions. |
| Verified identity | 8/10 | Publisher declared (repository, package or homepage) and domain control verified on agent-tools.cloud (company-registry check not available yet). |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 4/5 | Declares OAuth (MCP authorization requires PKCE). |
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive
(1819 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.
Compared with peers
Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.
- Readiness
- Higher than 100% of peers
- This listing 93 · peer median 81
- Latency
- Faster than 5% of peers
- This listing 1,570 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
- Verified identity −2
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage) and domain control verified on agent-tools.cloud (company-registry check not available yet).
- Freshness + modern flags −1
— Keep the listing current in the registry or source it comes from.
Now: seen in a source within 7 days.
Listed in
Directories this entry was found in.
mcp-registry since 2026-11-05
How to connect
MCP endpoint (streamable-http)
https://uetr.ai/mcp
JSON-RPC initialize probe
curl -X POST https://uetr.ai/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://uetr.ai/mcp