swapeazi MCP server

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

• discover_payment

  “Starts a cross-border payment: prices it on every rail (bank, PSP, stablecoin) and lists what is not known, before anything is prepared.”

  Publisher declares: read-only yes · open-world yes

  13 inputs, 3 required

  • amountnumberrequired“The amount, greater than zero.”
  • source_currencystringrequired“ISO 4217 code the payment leaves in, e.g.”
  • target_currencystringrequired“ISO 4217 code the payment must land in, e.g.”
  • directionstring“pay (default): amount is what leaves.”
  • amount_instring“Which currency amount is stated in.”
  • needed_bystring“Optional ISO date the money must land by.”
  • release_atstring“Optional ISO date-time the payment will be released; default now.”
  • payerobject“Optional.”
  • rails_allowedarray“Default: all.”
  • current_quoteobject“Optional: a quote already held, measured as given against the reference.”
  • constraintsobject“Optional.”
  • clientobject“Optional.”
  • detailstring“compact (default): a short summary that points at the signed full document, sized for a tool result.”
• run_payments

  “Prepares a batch of cross-border payments for approval: validates each payee, prices each route and drafts each instruction for the business's own bank, provider or wallet.”

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

  11 inputs

  • sampleboolean“true: the built-in sample run (synthetic, labelled), no key needed.”
  • source_currencystring“The currency the business pays from, e.g.”
  • payablesarray“[{ reference, payee: { name, iban?, bic?, account_number?, routing_number?, branch_code?, country?”
  • filestring“Instead of payables: a payout CSV or pain.001 text.”
  • previousarray“The previous run's payables, for changed bank details and amount jumps.”
  • policyobject“{ approver_role, material_threshold: { amount, currency }, agent_may_record_approval }”
  • sortstring“Your chosen order for the routes: landed cost against the official rate, stated days to land, or the measured 7-day answer rate.”
  • include_typesarray“Keep only routes of these rail types.”
  • exclude_typesarray“Leave out routes of these rail types.”
  • min_answer_ratenumber“Percent, 0 to 100: leave out routes whose measured 7-day answer rate is lower, or not measured (not enough reads).”
  • access_keystring“A router key (rk_...), if not sent as a Bearer header.”
• approve_payment_run

  “Gets prepared payments approved by a named person and returns each one's release instruction.”

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

  5 inputs, 2 required

  • run_idstringrequired“pr_...”
  • approverobjectrequired“{ name, role, id?”
  • payments“"all_prepared" or a list of payment_ids.”
  • acknowledgeboolean“true to approve listed payments that need attention or have no evidence, once the person has assessed them.”
  • access_keystring“A router key (rk_...), if not sent as a Bearer header.”
• payment_run_status

  “Tracks each payment in a run from prepared through approval and release to what landed.”

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

  3 inputs, 1 required

  • run_idstringrequired“pr_...”
  • exportboolean“true: the audit export (JSON) instead of the run.”
  • access_keystring“A router key (rk_...), if not sent as a Bearer header.”
• recommend_payment_route

  “Selects a route for one payment, with the reasons.”

  Publisher declares: read-only yes · open-world yes

  15 inputs

  • invoice_textstring“Paste the invoice or a sentence (e.g.”
  • amountnumber“Amount, in currency (default the source currency).”
  • currencystring“The currency of amount: the source currency, or the destination one (then it is what the supplier receives).”
  • source_currencystring“ISO code you pay from, e.g.”
  • destination_currencystring“ISO code the supplier is paid in, e.g.”
  • destination_countrystring“ISO 3166 alpha-2 or name, e.g.”
  • beneficiary_amountnumber“What the supplier must receive, in the destination currency (instead of amount).”
  • due_datestring“YYYY-MM-DD: a route that cannot settle by then is not eligible.”
  • prioritystring“Sets the default scoring weights.”
  • weightsobject“Your own scoring weights: { total_cost, speed, reliability, liquidity, compliance }, non-negative, normalised to 1.”
  • existing_providerobject“Your current provider: { provider, kind: quote | entered_rate | past_payment, rate (destination per source unit) or landed_amount, fees: { transaction, interme…”
  • supplierstring“Optional.”
  • referencestring“Optional.”
  • analysis_idstring“Read a kept analysis (pa_...) instead of making a new one.”
  • access_keystring“A router key (rk_...), if not sent as a Bearer header: names the routes and is not counted.”
• assess_route

  “Prices a cross-border payment before the business commits to it: every known route for the pair, assessed on SwapEazi's independent data.”

  Publisher declares: read-only yes · open-world yes

  13 inputs

  • fromstring“Source currency, ISO code, e.g.”
  • tostring“Destination currency, ISO code, e.g.”
  • corridorstring“Instead of from and to: e.g.”
  • amountnumber“Amount leaving, in the source currency.”
  • as_ofstring“Assessment time, ISO 8601, within 15 minutes of now (default now).”
  • assessment_idstring“Retrieve a kept assessment record instead of making a new one.”
  • sortstring“Your chosen order for the routes: landed cost against the official rate, stated days to land, or the measured 7-day answer rate.”
  • include_typesarray“Keep only routes of these rail types.”
  • exclude_typesarray“Leave out routes of these rail types.”
  • min_answer_ratenumber“Percent, 0 to 100: leave out routes whose measured 7-day answer rate is lower, or not measured (not enough reads).”
  • payer_countrystring“Two-letter country the money leaves from.”
  • beneficiary_countrystring“Two-letter country of the beneficiary's account; with payer_country for a same-currency payment.”
  • charge_optionstring“Who pays the banks' charges on a wire: OUR (payer pays all), SHA (shared), BEN (beneficiary).”
• liquidity_map

  “Shows where a payment of this size can be filled, and at what cost.”

  Publisher declares: read-only yes · open-world yes

  7 inputs, 1 required

  • pairstring“e.g.”
  • fromstring“ISO 4217 code of the source currency (what leaves), e.g.”
  • tostring“ISO 4217 code of the destination currency (what lands), e.g.”
  • amountnumberrequired“Ticket size, in the from currency unless amount_currency says otherwise.”
  • amount_currencystring“The from or the to currency.”
  • prefundingobject“{ amount, currency?, corridor?, days_held }: an amount held to prefund the corridor, and for how many days (1 to 365).”
  • access_keystring“A router key (rk_...), if not sent as a Bearer header.”
• onchain_liquidity

  “Finds where a stablecoin payment of this size can be filled on-chain, and at what cost: for USDC and USDT (and ZARP, cNGN as to_asset), executable depth and cost at the amount on Ethereum, Tron, Sola…”

  Publisher declares: read-only yes · open-world yes

  6 inputs, 1 required

  • amountnumberrequired“The ticket in US dollars (dollar stablecoins at par).”
  • from_assetstring“USDC or USDT.”
  • to_assetstring“USDC, USDT, ZARP or cNGN (ZAR and NGN map to ZARP and cNGN).”
  • chainsarray“Any of ethereum, tron, solana, base, bsc, arbitrum, polygon.”
  • destinationstring“Optional supplier country, two letters (e.g.”
  • access_keystring“A router key (rk_...), if not sent as a Bearer header: shows exchange and P2P venue names in the destination block.”
• record_landed

  “Closes a payment once the money arrived, on its remembered intent: what left (source currency) and what arrived (destination currency), and/or attach a stablecoin leg by chain and transaction hash, v…”

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

  7 inputs, 1 required

  • intent_idstringrequired“The remembered intent to close (remembered.intent_id from route_intent).”
  • sentnumber“Amount that left, in the source currency.”
  • landednumber“Amount that arrived, in the destination currency, after every deduction.”
  • settled_atstring“YYYY-MM-DD”
  • providerstring“Defaults to the route selected on the last day.”
  • chainstring“For a stablecoin leg: base, ethereum, arbitrum, optimism, polygon or celo.”
  • txstring“For a stablecoin leg: the transaction hash; read and priced from the chain and added to the payment record.”
• reconcile_paymenton 1 other server

  “Reconciles each released payment in a run with what landed: amount sent, amount landed, settlement time, proof reference, the official rate with a Rate Receipt, realised all-in cost in percent and in…”

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

  4 inputs, 2 required

  • run_idstringrequired“pr_...”
  • dry_runboolean“true: validate only, write nothing.”
  • paymentsarrayrequired“[{ payment_id, sent_amount, landed_amount, settled_at?, proof_ref, source?”
  • access_keystring“A router key (rk_...), if not sent as a Bearer header.”
• record_release

  “Records the release of a material payment against the organisation's release policy, at the moment it is released: the map_id and measure_id on file, who released it, and any exception with its reaso…”

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

  11 inputs, 3 required

  • policy_idstringrequired“The organisation's release policy the payment is released under, e.g.”
  • payment_refstringrequired“Your internal payment reference, never an account number.”
  • uetrstring“The payment's SWIFT UETR (UUID v4), optional: ties the record to the payment itself.”
  • amountobject“The released amount: { value, currency }.”
  • map_idstring“The Options Map (map_id) on file for this payment, if one was made.”
  • measure_idstring“The Measure (msr_...) on file for this payment, if one was made.”
  • intent_hashstring“The intent_hash from compile_intent, so the record proves the map matches this payment.”
  • released_atstring“ISO timestamp; defaults to now.”
  • released_byobjectrequired“Who released the payment: { type: human | system | agent, id }.”
  • exceptionobject“Only when the release falls outside the policy: { reason, approved_by: { id, role } }.”
  • agent_approvalobject“Agent releases only: { id, role } of the person who signed off a release above the policy's agent_autonomy.release_up_to.”
• release_status

  “Tracks a released payment's evidence: reads its Release Evidence Record by rer_id: the policy result at release and the reconcile status as of now (pending, done, overdue or not required).”

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

  1 input

  • rer_idstring“Optional.”

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

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.