uetr.ai MCP server

None of its 33 tools are described as changing anything. For 33 the reading was uncertain, so no mark is shown.

• add_transfer

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

  Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

  3 inputs, 3 required

  • uetrstringrequired“The transfer's UETR.”
  • amountobjectrequired“The amount sent and its currency.”
  • payment_datestringrequired“The date the payment was sent.”
• archive_transfer

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

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  1 input, 1 required

  • uetrstringrequired“The transfer's UETR.”
• change_webhook_endpoint_url

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

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

  2 inputs, 2 required

  • idstringrequired“The webhook endpoint's id.”
  • urlstringrequired“The full HTTPS address.”
• create_webhook_endpointon 2 other servers

  “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.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world yes

  2 inputs, 1 required

  • urlstringrequired“The full HTTPS address.”
  • eventsarray“The events to send.”
• decline_team_invitation

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

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  1 input, 1 required

  • tokenstringrequired“The token from the recipient's invitation link.”
• delete_transfer

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

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  1 input, 1 required

  • uetrstringrequired“The transfer's UETR.”
• delete_webhook_endpointon 2 other servers

  “Delete a webhook endpoint.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  1 input, 1 required

  • idstringrequired“The webhook endpoint's id.”
• export_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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input

  • cursorstring“The next_cursor of the previous page: the last UETR on that page.”
• get_accounton 133 other servers

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

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• get_billing_linkon 2 other servers

  “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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• get_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.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • record_tokenstringrequired“The token at the end of a payment record link (/p/...), or the whole link.”
• get_plan_usageon 1 other server

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

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.