Home / MCP registry index / ai.uetr/uetr.ai

uetr.ai - UETR and SWIFT Payment Tracking

ai.uetr/uetr.ai in the official MCP registry. Endpoint https://uetr.ai/mcp.

The registry describes it as: UETR tracking and SWIFT payment tracking for AI apps. Read transfer status and manage monitoring.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http uetr-ai https://uetr.ai/mcp

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

code --add-mcp '{"name":"uetr-ai","type":"http","url":"https://uetr.ai/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

add_transfer archive_transfer change_webhook_endpoint_url create_webhook_endpoint decline_team_invitation delete_transfer delete_webhook_endpoint export_transfers get_account get_billing_link get_payment_record get_plan_usage get_share_link get_transfer get_watcher_count get_webhook_endpoint invite_team_member list_pending_access list_team_members list_transfers list_webhook_deliveries list_webhook_endpoints recheck_transfer remove_team_member rename_transfer resend_team_invitation restore_transfer rotate_webhook_secret send_webhook_test set_check_frequency share_payment_record update_transfer update_webhook_endpoint

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-05): 3e3a4f8aa54cefdc. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/ai-uetr-uetr-ai/badge.svg)](https://lazaretto.dev/mcp-registry/ai-uetr-uetr-ai)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Monitoring and observability MCP servers