Skip to content

SwapEazi MCP server

io.github.MsingathiM/swapeaziMsingathiMstreamable-httpv2.5.0Scanned

Payment intelligence for agents sending money abroad or paying suppliers.

74 tools: 2 can delete or cancel things, 32 do something that can't be undone, 21 change things and 19 only read.

Tools: 2 delete, 32 irreversible, 21 write, 19 read.
  • Reads private data · 0
  • Reads text others write · 42
  • Can send data out · 18
  • 27 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things and 32 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SwapEazi MCP server can do

The SwapEazi MCP server is published by the GitHub account MsingathiM. It has 74 tools. It can delete or cancel things (2 tools: remove_rail_account and submit_payment), do things that cannot be undone, such as sending, paying or publishing (discover_payment, run_payments, approve_payment_run, payment_run_status and 28 more) and create or change data (21 tools: record_landed, record_release, books_record, swapeazi_coverage and 17 more). 19 tools only read.

42 tools bring in text other people can write (discover_payment, run_payments, recommend_payment_route and 39 more); 18 tools can send data out of your system (assess_route, swapeazi_corridor_registry, swapeazi_beneficiary_check and 15 more).

The fixed checks matched 27 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 2.5.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

74 tools

Deletes or cancels 2Claude Code: deny
  • remove_rail_accountKeyed.1 finding

    Why it is in this group

    • The name "remove_rail_account" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...a connected rail account and its stored credentials. Payments already sent stay readable in..."

      What this check looks for
    Description, as the server wrote it
    Keyed. Deletes a connected rail account and its stored credentials. Payments already sent stay readable in the business's own rail account.

    Annotations the server declares

    • title: Remove a connected rail account
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • submit_paymentSends ONE approved, released payment of a run through the business's own connected rail account (sandbox), with an idempotency key; without connection_id it reads the submission's …Reads text others writeNo findings

    Why it is in this group

    • The name "submit_payment" says "submit": a word for a change.
    • The name "submit_payment" also says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Sends ONE approved, released payment of a run through the business's own connected rail account (sandbox), with an idempotency key; without connection_id it reads the submission's status. Refused unless approved and within the connection's cap. Production execution waits on an authorised provider agreement.

    Annotations the server declares

    • title: Submit an approved payment (sandbox)
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Can't be undone 32Claude Code: ask
  • add_payment_outcomeAdds one payment the caller made to the SwapEazi Payment Index, voluntarily: currencies, amount sent, amount landed (after every deduction), the date it landed and the route type.Reads text others writeNo findings

    Why it is in this group

    • The name "add_payment_outcome" says "add": a word for a change.
    • The name "add_payment_outcome" also says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Adds one payment the caller made to the SwapEazi Payment Index, voluntarily: currencies, amount sent, amount landed (after every deduction), the date it landed and the route type. SwapEazi works out the all-in cost against that day's reference with its landed-cost arithmetic and publishes the row as SELF-REPORTED; with a receipt or statement in files it is read and matched to the figures (amounts within 0.5%, date within 3 days) and published as VERIFIED, and the file is not kept unless keep_file is true. Refused with the reason when a field is invalid, the date is in the future or over two years old, the day has no reference, or the amounts are more than 15% from it. Costs below -50 or above 800 bps, or payments over USD 25m, are held for review, not published. No names, company or account details are taken; the provider is masked (e.g. 'a South African bank') unless show_provider is true. Returns a withdraw token. Same as POST /api/v1/index/payments.

    Annotations the server declares

    • title: Add a payment to the Payment Index
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • approve_payment_runGets prepared payments approved by a named person and returns each one's release instruction.No findings

    Why it is in this group

    • The name "approve_payment_run" says "approve": a word for a change.
    • The name "approve_payment_run" also says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Gets prepared payments approved by a named person and returns each one's release instruction. Records the approval of that person (approver: { name, role }) for the run's prepared payments (payments: "all_prepared") or listed payment_ids (held ones need acknowledge: true), and creates one release record per approved payment. Each approved payment returns release_in_own_bank: beneficiary, amount, currency, reference, which of the business's own accounts to pay from and the cut-off, for the business to release itself in its own bank or rail portal; then record what landed with reconcile_payment. An agent cannot approve on its own: this tool records an approval only when the run's policy sets agent_may_record_approval and names the person who approved; otherwise it returns how the person approves (POST /api/v1/payment-runs/{id}/approve). Never sends or moves money.

    Annotations the server declares

    • title: Record a named person's approval of a payment run
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • assess_routePrices a cross-border payment before the business commits to it: every known route for the pair, assessed on SwapEazi's independent data.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "assess_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Prices a cross-border payment before the business commits to it: every known route for the pair, assessed on SwapEazi's independent data. Returns deterministic JSON: the routes known for the pair, each cost and FX figure with its source, read time, freshness (fresh, aging, stale, unknown) and evidence type (observed, executable, indicative, published; the official rate as reference), settlement facts, the requirements on record with sources, what changed since the last assessment of the corridor, data-quality flags (stale, contradictory, missing, indicative only), unknowns, and the evidence behind each finding, under an assessment_id whose record is kept and retrievable (GET /api/v1/route-assessments/{id}; a content hash, not a signature). Never ranks a route as advice, never executes, never claims a figure is executable unless a provider's firm quote is on record. Free; same as GET /api/v1/route-assessments.

    Annotations the server declares

    • title: Assess a cross-border payment route before paying
    • readOnlyHint: true
    • openWorldHint: true
  • calculate_payment_costWhat this payment costs through your current provider against the official rate: effective rate, FX spread, transaction, intermediary and payout fees, total cost in money and bps, …Reads text others write1 finding

    Why it is in this group

    • The name "calculate_payment_cost" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "calculate_payment_cost" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "calculate_payment_cost" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    What this payment costs through your current provider against the official rate: effective rate, FX spread, transaction, intermediary and payout fees, total cost in money and bps, and what the beneficiary receives; with each alternative route's cost at the same size. One analysis (POST /api/v1/payment-analyses), the same service for every payment-intelligence tool. Every figure labelled LIVE, INDICATIVE, HISTORICAL or ESTIMATED; estimated savings are never realised. Free: shares the route-assessment allowance.

    Annotations the server declares

    • title: Calculate what a payment costs
    • readOnlyHint: true
    • openWorldHint: true
  • check_fx_chargesEvery foreign-currency cost on a bank or card statement found, proven and booked.1 finding

    Why it is in this group

    • The name "check_fx_charges" says "charge": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "check_fx_charges" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_fx_charges" says "charge": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Every foreign-currency cost on a bank or card statement found, proven and booked. Give files (statement CSV, or PDF/screenshot; supplier invoices) or transactions[] and invoices[]. Each charge is matched to its invoice, rated at the ECB mid of the transaction date (last business day on weekends and holidays, date and source named), split into hidden markup in the rate, disclosed fee and VAT, booked as balanced journals in the functional currency (settings: functional_currency, chart_of_accounts, accounting_policy), with exceptions flagged (verification charges, failed attempts, refunds netted, no conversion, vendor reference rates never trusted, cashback, duplicates blocked). Returns a signed, re-runnable pack: same input, same pack_id, hashes and signature. Read-only: never holds or moves money. Free up to 20 transactions a month; unlimited with a key.

    Annotations the server declares

    • title: FX Agent: check a statement's FX charges
    • readOnlyHint: true
    • openWorldHint: false
  • check_payment_against_mandateVerify one payment against a mandate before it is prepared.Can send data out1 finding

    Why it is in this group

    • The name "check_payment_against_mandate" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "check_payment_against_mandate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_payment_against_mandate" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Verify one payment against a mandate before it is prepared. A breach returns mandate_violation and the rule that failed. A pass still needs the named person to approve. Nothing is sent. A router key is required. The verification is recorded when the payment is prepared inside a payment run.

    Annotations the server declares

    • title: Hold one payment against a mandate
    • readOnlyHint: true
    • openWorldHint: false
  • check_provider_liquiditySpec v1.0 name for liquidity_map: each venue type with whether the evidence read shows depth at the size, slippage and landing cost with a Rate Receipt, or Being measured with the …Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "check_provider_liquidity" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Spec v1.0 name for liquidity_map: each venue type with whether the evidence read shows depth at the size, slippage and landing cost with a Rate Receipt, or Being measured with the reason. Same arguments as liquidity_map.

    Annotations the server declares

    • title: Liquidity at this payment's size
    • readOnlyHint: true
    • openWorldHint: true
  • compile_intentTurn a corporate FX or payment requirement into a PaymentIntent: the currencies, the amount and whether it is what leaves or what must land, the value date, and the principal's own…Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "compile_intent" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Turn a corporate FX or payment requirement into a PaymentIntent: the currencies, the amount and whether it is what leaves or what must land, the value date, and the principal's own constraints. Accepts a sentence ('pay a Japanese supplier JPY 800m by 15 October') with the source currency, a flat form, or a full intent. The source currency is never assumed. Returns the intent, its hash and every assumption made. Free.

    Annotations the server declares

    • title: Structure a payment intent
    • readOnlyHint: true
    • openWorldHint: false
  • confirm_paymentAfter your wallet has sent a payment prepared by prepare_payment, give its prepare_id and transaction hash.Reads text others writeNo findings

    Why it is in this group

    • The name "confirm_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    After your wallet has sent a payment prepared by prepare_payment, give its prepare_id and transaction hash. SwapEazi reads the receipt on chain, verifies it came from the prepared wallet and matches the prepared transaction, and returns a signed payment record for the audit trail. Read-only on chain; moves nothing.

    Annotations the server declares

    • title: Confirm a prepared payment on chain
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • coverageHow much of the map for a currency pair and size rests on evidence: the coverage tier (evidenced, partial or inferred), how many reconciled outcomes sit behind it, how many candida…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "coverage" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    How much of the map for a currency pair and size rests on evidence: the coverage tier (evidenced, partial or inferred), how many reconciled outcomes sit behind it, how many candidates carry economics, the reference's publishers, error band and type (hard_peg, derived_peg, fixing_median or home_central_bank), and whether a failure rate is published yet. With country (e.g. CI for XOF), also that country's profile and measured receipts. Free.

    Annotations the server declares

    • title: Coverage for a pair and size
    • readOnlyHint: true
    • openWorldHint: true
  • discover_paymentUse when a user wants to send money abroad or pay a supplier, for example 'pay GBP 1,000 to Botswana' or 'send EUR 1,000 to Botswana'.Reads text others write1 finding

    Why it is in this group

    • The name "discover_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "discover_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "discover_payment" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Use when a user wants to send money abroad or pay a supplier, for example 'pay GBP 1,000 to Botswana' or 'send EUR 1,000 to Botswana'. Ask for the recipient currency if it is not specified; do not assume it from the country. Provide amount, source_currency and target_currency, and beneficiary.country when known. Returns available payment evidence, costs, timing, requirements and unknowns for the currency pair; coverage varies and some facts may be unavailable. A reference rate or indicative figure is not a firm quote. The compact response points to a signed Options Map; detail: "full" returns the full report. An optional needed_by adds timing and FX scenarios, not a forecast or recommendation. The customer decides and their provider executes the payment.

    Annotations the server declares

    • title: Payment Discovery
    • readOnlyHint: true
    • openWorldHint: true
  • get_payment_guideA payment guide for a business paying or getting paid in Namibia, from one sentence, e.g.Reads text others write1 finding

    Why it is in this group

    • The name "get_payment_guide" says "get": a word for reading.
    • The description's first verb is "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "get_payment_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "get_payment_guide" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    A payment guide for a business paying or getting paid in Namibia, from one sentence, e.g. 'We are a Dutch logistics company starting truck operations out of Walvis Bay, paying drivers and suppliers in Namibia' or 'We pay traders in Namibia from South Africa every month'. Leads with paying and getting paid: the banks, fintechs, stablecoin platforms and crypto routes on record that can carry the payment, with speed and the forms of money each takes and pays out; what a payment really costs against the rate a currency site shows, worked from SwapEazi's own measurements; and the payment rules that decide whether money can move (exchange control, the Common Monetary Area, the documents a bank asks for before releasing a cross-border payment, limits). Then funding until contracts pay (institutions that publicly offer working-capital, asset or trade finance; information only, SwapEazi never lends, brokers or introduces for a fee); outside payments, who to see (each authority with its link; registration, tax and permits are not explained: use a tax or legal practitioner); documented payment pitfalls; what is not known and the next three actions with who approves what. Every fact with its source URL, date and evidence class (published, register, reported, not published). Information with sources, not legal, tax or financial advice. Paid per call: x402 (USDC on Base, price in the 402 body, USD 0.25) via params._meta["x402/payment"], or a paid router key as Bearer. The free summary is POST https://swapeazi.io/api/v1/pay-guide. The agent prepares; a person decides. SwapEazi never touches the money.

    Annotations the server declares

    • title: Payment guide for one business
    • readOnlyHint: true
    • openWorldHint: true
  • join_networkKeyed.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Keyed. A business, a rail or an agent joins. A rail may attach a quote feed as an API key or an OAuth-style connection and one published rate. No placement is sold. SwapEazi does not hold or move money.

    Annotations the server declares

    • title: Join the network
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • payment_controlsRead the controls that govern the payments an agent prepares for an organisation: its spend profiles with today's and this month's spend against each budget, the payments waiting f…1 finding

    Why it is in this group

    • The name "payment_controls" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "payment_controls" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_controls" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Read the controls that govern the payments an agent prepares for an organisation: its spend profiles with today's and this month's spend against each budget, the payments waiting for a person to approve (with any transaction already prepared after approval), and the audit trail of prepared and confirmed payments. With approval_id, reads that one approval. Read-only. Needs the organisation's key.

    Annotations the server declares

    • title: Spend profiles, approvals and audit trail
    • readOnlyHint: true
    • openWorldHint: false
  • payment_indexLists real cross-border payment outcomes per corridor and size band: date, corridor, size band, route type (bank, payout_network, otc, exchange, stablecoin, card), the all-in cost …Can send data out1 finding

    Why it is in this group

    • The name "payment_index" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "payment_index" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_index" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Lists real cross-border payment outcomes per corridor and size band: date, corridor, size band, route type (bank, payout_network, otc, exchange, stablecoin, card), the all-in cost in bps against the official or mid-market reference of that day, what the figure is (a payment that landed, receipt figures, a quoted rate, a published rate, a P2P advert median) and a source label on every row: MEASURED (SwapEazi's own reads and receipts), PUBLIC REPORT (a published rate, with its link), SELF-REPORTED (submitted by a business) or VERIFIED (submitted with a receipt SwapEazi matched). Also medians per corridor, size band and source; sources are never pooled. Providers are masked unless the submitter chose to name them. A record, not advice, not a quote and not a ranking. Free; same as GET /api/v1/index/payments.

    Annotations the server declares

    • title: Read the SwapEazi Payment Index
    • readOnlyHint: true
    • openWorldHint: false
  • payment_intentKeyed.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Keyed. A business states the payee, the corridor, the amount the payee must receive, and the deadline. Returns a proposal: bank, OTC, ramp, AMM and secure P2P wallet routes, including the business's own negotiated rate when one is on record. The selected route is the lower total the payer sends to land the full amount by the deadline. Each figure is measured, a public quote read at a date and not locked, or Being measured. SwapEazi does not hold or move money. A person still approves.

    Annotations the server declares

    • title: State what the business owes
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • payment_run_statusTracks each payment in a run from prepared through approval and release to what landed.1 finding

    Why it is in this group

    • The name "payment_run_status" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "payment_run_status" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_run_status" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Tracks each payment in a run from prepared through approval and release to what landed. Reads the run by run_id: each payment's status (prepared, needs_attention with reasons, no_evidence), its assessment and Rate Receipts, approval, release record and what landed. export: true returns the audit export, where any payment without an assessment, approval or release record shows "no evidence". pr_sample needs no key; a real run needs the router key that made it.

    Annotations the server declares

    • title: A payment run's status, per payment, or its audit export
    • readOnlyHint: true
    • openWorldHint: false
  • payout_preflightPre-release check on a whole payout file before it goes to the company's own bank or PSP.1 finding

    Why it is in this group

    • The name "payout_preflight" says "payout": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "payout_preflight" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payout_preflight" says "payout": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Pre-release check on a whole payout file before it goes to the company's own bank or PSP. Send the file's text: an ISO 20022 pain.001 credit-transfer file (versions .03 to .12) or a CSV with a header row (comma or semicolon, Dutch or English column names). Every row comes back ok, needs_person or blocked, with the reasons: missing name or account, failed IBAN checksum, a BIC from a different country than the IBAN, SA branch code, SADC mobile money, too many decimals, a euro payment outside SEPA, an execution date in the past or on a weekend, possible duplicates, and rows above the company's own review limit. With a signing key set, it also returns a signed record of the check (file hash and each row's state, no names or accounts). SwapEazi never sends, holds or routes the money: the company releases the file itself. Paid: configure this server with an Authorization Bearer key (https://swapeazi.io/pricing).

    Annotations the server declares

    • title: Assess a payout file before it is released
    • readOnlyHint: true
    • openWorldHint: false
  • payout_rulesWhich payout rules reach a payout, and when: for a corridor (two-letter countries, or currencies) and a route (bank or stablecoin), each rule SwapEazi holds answers applies, depend…Can send data out1 finding

    Why it is in this group

    • The name "payout_rules" says "payout": a word that usually means money moves, which cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "payout_rules" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payout_rules" says "payout": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Which payout rules reach a payout, and when: for a corridor (two-letter countries, or currencies) and a route (bank or stablecoin), each rule SwapEazi holds answers applies, depends (and on what) or does not apply, with its dated steps, its official document and the day it was read. Drafts are never answered as law. Information from each rule's own document, not legal advice. route_intent carries the rules that reach its payout in its rules field. Read-only, free, no key.

    Annotations the server declares

    • title: Payout rules: does it apply, and when
    • readOnlyHint: true
    • openWorldHint: false
  • prepare_paymentPrepare an unsigned USDC or USDT transaction for the paying wallet you control, on Base, Arbitrum, Optimism, Polygon or BNB Chain, or USDT (TRC-20) on Tron (chain_id 728126428, T..…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "prepare_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Prepare an unsigned USDC or USDT transaction for the paying wallet you control, on Base, Arbitrum, Optimism, Polygon or BNB Chain, or USDT (TRC-20) on Tron (chain_id 728126428, T... addresses; TronLink signs it). SwapEazi screens the recipient's address and verifies the organisation's spend profile first: the cap per payment, the daily and monthly budget, approved recipients and chains, and the approval line. A person approves every payment an agent prepares: within the rules it returns an approval_id, the approver decides at /approvals, and once approved payment_controls with that approval_id returns the transaction (a plain transfer, or a swap or bridge with no SwapEazi fee) for your wallet to sign; outside the rules it explains why. Pass the map_id and candidate_id of the stablecoin option you took from discover_payment or map_options, so the approver sees what the guide showed for it and the records name the map; the guide never picks it. SwapEazi never signs, holds keys or moves funds. With private: true, the payment runs through NEAR Intents' confidential mode under the same rules; that is also the way between Tron and an EVM chain. With profile_id, needs the organisation's key.

    Annotations the server declares

    • title: Prepare a stablecoin payment within the rules
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • prepare_payment_instructionSpec v1.0 name for run_payments: prepares each payment (payee validation, route assessment, instruction, approval digest) and returns each payment's lifecycle state.Reads text others writeNo findings

    Why it is in this group

    • The name "prepare_payment_instruction" says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Spec v1.0 name for run_payments: prepares each payment (payee validation, route assessment, instruction, approval digest) and returns each payment's lifecycle state. Never approves or sends. Same arguments as run_payments; sample: true for the synthetic run.

    Annotations the server declares

    • title: Prepare payment instructions
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • rail_positionKeyed.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "rail_position" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Keyed. For one corridor, the rail's own published rate beside the official rate and a public market read when one exists. Position is lower_landed_cost, higher_landed_cost or unknown. A missing figure is Being measured.

    Annotations the server declares

    • title: Where a rail's published price sits
    • readOnlyHint: true
    • openWorldHint: true
  • rate_deal_historyKeyed.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "rate_deal_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Keyed. Returns the dated history of comparisons for one customer and corridor: the rate on each prepared or reconciled payment against that day's official rate, the negotiated deal (margin in bps or a fixed spread, with the customer's own bank label), and a public market price when one was read. Drift is in bps and in the sent currency. above_negotiated is set when the gap over the deal exceeds the stored tolerance. A missing figure is null. The payment stays with the customer's own bank. A router key is required.

    Annotations the server declares

    • title: Dated comparisons against a customer's bank deal
    • readOnlyHint: true
    • openWorldHint: false
  • recommend_payment_routeLists the routes for one payment side by side, with cost, speed, licence and freshness.Reads text others write1 finding

    Why it is in this group

    • The name "recommend_payment_route" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "recommend_payment_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "recommend_payment_route" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Lists the routes for one payment side by side, with cost, speed, licence and freshness. Hard facts first (complete cost, not stale, settles by the due date, licence active, not excluded by route health). SwapEazi does not pick a route. A person chooses. Not a firm quote: confirm with the provider before approval. One analysis (POST /api/v1/payment-analyses), the same service for every payment-intelligence tool. Every figure labelled LIVE, INDICATIVE, HISTORICAL or ESTIMATED. Free: shares the route-assessment allowance.

    Annotations the server declares

    • title: List routes for one payment
    • readOnlyHint: true
    • openWorldHint: true
  • reconcile_paymentReconciles 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 cos…No findings

    Why it is in this group

    • The name "reconcile_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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 the sent currency, and position inside, above or below the assessment range. The same proof reference is rejected the second time. dry_run: true validates and writes nothing. A payment with no assessment is flagged no_evidence. A router key is required except for pr_sample. Never sends money.

    Annotations the server declares

    • title: Reconcile what landed on a payment run
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • request_payment_approvalFor a payment run: the payments awaiting approval with amount, route, assessment and approval_digest, the approver role, and the payments not ready with their lifecycle state and r…1 finding

    Why it is in this group

    • The name "request_payment_approval" says "request": a word for a change.
    • The name "request_payment_approval" also says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "request_payment_approval" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "request_payment_approval" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    For a payment run: the payments awaiting approval with amount, route, assessment and approval_digest, the approver role, and the payments not ready with their lifecycle state and reason. Never approves: a named person approves with approve_payment_run.

    Annotations the server declares

    • title: What needs a person's approval
    • readOnlyHint: true
    • openWorldHint: false
  • route_intentRoute one cross-border payment, given as fields or as one sentence ("USD 25,000 to a supplier in Lagos by 30 November").Reads text others writeCan send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Route one cross-border payment, given as fields or as one sentence ("USD 25,000 to a supplier in Lagos by 30 November"). From a sentence the guide reads what matters without being told: urgency or the due date sets the deadline and puts speed first, words such as cheapest put cost first, regulated or licensed keeps only providers with a licence on record, and paying drivers, staff or a supplier is noted; intent.understood says what was read, and explicit policy fields override it. Returns every route that can carry it, ordered by the payer's own policy, the route the policy selects on the strongest evidence (payments measured when they landed, then published prices; estimates only if the policy allows), the saving against the payer's own quote, and where to pay. With a due date it also routes across time: pay now, lock a forward while holding tokenised T-bills, convert and park, or hold unhedged, as what each needs today. With remember: true SwapEazi keeps the intent, reprices it daily until due and returns its intent_id. A sentence about idle money ("park $5m USDC, back within 24 hours, non-US, qualified, we have Ondo") returns treasury parking instead: tokenised T-bill funds that fit the amount, eligibility, chain and redemption need, by net yield, with what the accounts already held can do and what a new account is worth. The free verification returns the verdict with names masked; a router key (Bearer rk_...) unlocks them. SwapEazi executes nothing and takes no fee from any provider. Returns a compact view by default (each route with its release window cut to the summary and landing dates); pass detail: "full" for everything.

    Annotations the server declares

    • title: Route an intent
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • run_paymentsPrepares 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.Reads text others writeNo findings

    Why it is in this group

    • The name "run_payments" says "run": a word for a change.
    • The name "run_payments" also says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Send the payables (payables: a JSON list; file: a payout CSV or pain.001; or xero: a Xero bills reply) with source_currency. Each payment is verified (changed bank details against previous, duplicates, missing fields), assessed (route assessment_id with Rate Receipts: who published each figure, when it was read, its evidence type) and given an instruction for the business's own bank, provider or wallet (a CSV row, or an unsigned stablecoin transaction). Each is prepared, needs_attention (with the reason) or no_evidence. Returns run_id. An agent prepares; a named person approves. Never sends or moves money. A router key runs real payables; without one, sample: true returns the synthetic sample run. Same as POST /api/v1/payment-runs.

    Annotations the server declares

    • title: Run a batch of cross-border payments: assess, assess, prepare
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • swapeazi_corridor_registryDocumented status of cross-border corridors per provider: which pairs a provider says it serves, published fees, and when each record was last verified.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "swapeazi_corridor_registry" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Documented status of cross-border corridors per provider: which pairs a provider says it serves, published fees, and when each record was last verified. Public tier only. Free, no key.

    Annotations the server declares

    • title: Corridor registry, public tier
    • readOnlyHint: true
    • openWorldHint: false
  • swapeazi_forwardThe estimated fair forward rate for a currency pair and tenor, by covered interest parity from an independent mid and central bank policy rates, with its margin of error, and what …Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "swapeazi_forward" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    The estimated fair forward rate for a currency pair and tenor, by covered interest parity from an independent mid and central bank policy rates, with its margin of error, and what hedging costs or earns per year. Free. With a paid key and quotedRate, the forward a bank quoted is held to it: how much is margin.

    Annotations the server declares

    • title: Fair forward and hedge cost
    • readOnlyHint: true
    • openWorldHint: true
  • tokenized_finance_intelFor a currency pair, explain documented tokenised deposit networks and payment instruments, their evidence status, access constraints and unknowns.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "tokenized_finance_intel" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    For a currency pair, explain documented tokenised deposit networks and payment instruments, their evidence status, access constraints and unknowns. A currency match is only a lead: it never confirms participating banks, executable FX liquidity, local payout, fees or end-to-end timing. Investment assets are excluded as payment routes. Free returns a concise masked preview; a paid key for this pair unlocks source-linked detail. No execution or advice.

    Annotations the server declares

    • title: Tokenised finance and settlement intelligence
    • readOnlyHint: true
    • openWorldHint: true
  • track_payment_settlementSpec v1.0 name for payment_run_status: each payment's lifecycle state (CREATED, ANALYSED, QUOTED, ROUTE_SELECTED, AWAITING_APPROVAL, APPROVED, SUBMITTED, PROCESSING, SETTLED, FAILE…1 finding

    Why it is in this group

    • The name "track_payment_settlement" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "track_payment_settlement" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "track_payment_settlement" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Spec v1.0 name for payment_run_status: each payment's lifecycle state (CREATED, ANALYSED, QUOTED, ROUTE_SELECTED, AWAITING_APPROVAL, APPROVED, SUBMITTED, PROCESSING, SETTLED, FAILED, REJECTED, EXPIRED, CANCELLED, REQUIRES_REVIEW) with the reason. SETTLED only on the provider's own confirmation.

    Annotations the server declares

    • title: Track a payment to settlement
    • readOnlyHint: true
    • openWorldHint: false
Changes things 21Claude Code: ask
  • books_recordA books-ready, standards-referenced record of one managed payment for the payer's own books: the invoice in the functional currency at approval and at settlement at dated official …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    A books-ready, standards-referenced record of one managed payment for the payer's own books: the invoice in the functional currency at approval and at settlement at dated official rates (ECB for EUR, SARB for ZAR, named with date), fees split out, the realised FX difference between approval and settlement, the conversion cost against the official rate, the landed amount, stablecoin legs each valued at its own time with the measured premium (classification left to the company's accountant), and the Rate Receipt and release record ids. Give run_id (+ payment_id) for a Payment Run (pr_sample works without a key), or the figures (business, payment, legs). format: json (record + suggested journal lines, accounts left to the company), csv or journal. closing: { date, currencies } adds the period-end closing rate for open balances. SwapEazi posts nothing to any ledger and decides no accounting policy.

    Annotations the server declares

    • title: Books-ready record for a payment
    • readOnlyHint: true
    • openWorldHint: false
  • check_constraintsRe-evaluate every candidate in a stored Options Map against constraints supplied now: the principal's own policy, an AP2 open (intent) mandate, a Verifiable Intent credential, or x…2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...n (intent) mandate, a Verifiable Intent credential, or x402 payment requirements (accepts[..."

      What this check looks for
    • Info

      The input schema at properties.verifiable_intent.description mentions "credential".

      Matched text

      inputSchema.properties.verifiable_intent.description: "A Verifiable Intent credential: the serialised SD-JWT, or decoded mand..."

      What this check looks for
    Description, as the server wrote it
    Re-evaluate every candidate in a stored Options Map against constraints supplied now: the principal's own policy, an AP2 open (intent) mandate, a Verifiable Intent credential, or x402 payment requirements (accepts[] with the listed price, verified against the reference). Each row comes back inside, outside or unknown, and carries the map's own route_family, regulatory_risk and onboarding_status/onboarding_gap for that candidate, so an agent can drop ineligible or blocked rows without a second call. Nothing is executed or issued. Free.

    Annotations the server declares

    • title: Hold a map to constraints
    • readOnlyHint: true
    • openWorldHint: false
  • connect_rail_accountKeyed.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ret and a required cap per payment. The credentials are proven with a read (no payment is s..."

      What this check looks for
    Description, as the server wrote it
    Keyed. Connects the business's OWN account at a rail (yellowcard) for reads and sandbox sending; production sending is off unless the deployment enables it, and the default flow is that the business releases payments itself in its own portal with its API key and secret and a required cap per payment. The credentials are proven with a read (no payment is sent), encrypted at rest and never returned: answers show the key's last four characters and the created date. Prefer POST /api/v1/rail-connections from your own software: credentials passed here travel through the agent's context. SwapEazi holds no funds and has no account in the flow.

    Annotations the server declares

    • title: Connect your own rail account
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • corridor_eventsDated corridor news for a currency pair or one currency: provider route launches and exits, licences granted or revoked, central-bank FX and payment rule changes, devaluations, lim…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Dated corridor news for a currency pair or one currency: provider route launches and exits, licences granted or revoked, central-bank FX and payment rule changes, devaluations, limit changes and outages, collected from payments press and regulator feeds across Africa, Latin America, Asia, the Middle East and Turkey. Each event carries its source link and an evidence label: 'official source' (a regulator or central bank published it), 'announced, unverified' (a company or the press reported it), or 'headline only, not read'. Listed newest first; route launches for the exact pair come back separately as announced_routes, never as payment options. Free.

    Annotations the server declares

    • title: Corridor news for a pair or currency
    • readOnlyHint: true
    • openWorldHint: true
  • create_mandateCreate a spend mandate for an agent: per-payment cap, period cap, currencies, corridors, rails (bank, provider, stablecoin_wallet), optional cap on cost above the official rate, th…No findings

    Why it is in this group

    • The name "create_mandate" says "create": a word for a change.
    Description, as the server wrote it
    Create a spend mandate for an agent: per-payment cap, period cap, currencies, corridors, rails (bank, provider, stablecoin_wallet), optional cap on cost above the official rate, the person who approves, and an expiry. A router key is required. A person still approves every payment. The mandate does not send money.

    Annotations the server declares

    • title: Create a per-agent spend mandate
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • decide_intentKeyed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Keyed. A named person approves or rejects a payment intent. The decision is kept with the time, the person and the proposal. An agent cannot approve alone. Nothing is sent.

    Annotations the server declares

    • title: A named person approves or rejects a proposal
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • map_optionsThe signed Options Map for a PaymentIntent: every rail and provider the graph holds for the pair and size, each with its access facts, documented capacity, settlement window, econo…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The signed Options Map for a PaymentIntent: every rail and provider the graph holds for the pair and size, each with its access facts, documented capacity, settlement window, economics basis (observed, band or unpublished) and evidence class, and whether it sits inside, outside or unknown against the principal's constraints. Each candidate also carries route_family (bank_correspondent or stablecoin_casp), regulatory_risk (stable, watch, restricted or blocked, tied to a tracked rule) and onboarding_status (ready, onboardable, ineligible or unknown, with onboarding_gap naming what's missing) so an agent can filter out ineligible or blocked routes before quoting. route_families lists every family even one with zero candidates, reason no_eligible_provider, rather than hiding it. Sorted by coverage tier, rail class and name, never by a rank. payout_rules lists the rules that reach the payout per route (applies or depends, each with its document; document_not_read when found by search). A guide, not advice. Pass an intent (any form compile_intent takes, including payer) or an intent_id. Free within the daily allowance; a key lifts it. Returns a compact view by default (one short object per candidate, every unknown in full) that points at the signed full map; pass detail: "full" for the whole signed document, or map_id to read back a map made earlier.

    Annotations the server declares

    • title: Map the options for an intent
    • readOnlyHint: true
    • openWorldHint: true
  • parallel_signalA dated series per currency of the gap between a public-advert median and the official rate.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    A dated series per currency of the gap between a public-advert median and the official rate. Labelled market-observed, never an official rate. Currencies: ZAR, MZN, MWK, ZMW, NGN, KES, BRL, ARS, PHP. Too few adverts, or no read on record, is null with a reason. A missing gap is never zero. Free.

    Annotations the server declares

    • title: Market-observed gap between public adverts and the official rate
    • readOnlyHint: true
    • openWorldHint: true
  • rail_handoffKeyed.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.channel_id): what the tool writes goes there.
    Description, as the server wrote it
    Keyed. With intent_id: after a person has approved, the approved instruction for your rail, with a Rate Receipt of the rate against the official rate and the negotiated deal; where no live connection is configured the adapter is marked stub. The default is that the business releases the payment itself in its own bank or rail portal (release_in_own_bank on the approved payment); SwapEazi never sends it. Sandbox only: with run_id, payment_id and connection_id, sends ONE Payment Run payment a named person approved through the business's OWN connected rail account (Yellow Card sandbox; production stays off unless the deployment sets YELLOWCARD_ENV=production), with the rail's own idempotency key, and returns the submission with a Rate Receipt and the release record. Refused, with the reason, without a recorded approval, when the payment changed since approval, above the connection's cap, or for an account other than the one approved. With run_id and payment_id only: reads that payment's status from the rail. SwapEazi holds no funds and has no account in the flow.

    Annotations the server declares

    • title: Handoff to your rail
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • reconcile_outcomeAfter the money moved: post what was sent and what landed (or the all-in cost) against the map it was chosen from.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    After the money moved: post what was sent and what landed (or the all-in cost) against the map it was chosen from. Returns the expected band beside the realised cost, signed. The outcome is kept by pair and size band only and later maps at that size carry it, so bands tighten and unknowns close. Economics only. Free.

    Annotations the server declares

    • title: Reconcile what landed
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • record_landedCloses 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 …Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "close": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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, verified from the chain. SwapEazi measures it against the independent reference and against what was routed, and every later route on the pair carries it as a measured payment. On a recurring intent it closes the current cycle only and the series moves to its next due date. Amounts only, never names or account numbers.

    Annotations the server declares

    • title: Record a landed intent
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • record_releaseRecords 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 excep…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 reason and approver. When an agent releases under a policy with agent_autonomy tiers, the record states the tier its amount falls in and the agent_approval on record for it. Returns a Release Evidence Record, appended to the organisation's hash chain and signed. It records; it never blocks, executes or moves money. A release with no map is still recorded, flagged as a policy miss. Needs the organisation's key.

    Annotations the server declares

    • title: Record a release
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • request_introductionRetired on 19 Oct 2026: SwapEazi collects no contact details for introductions.Reads text others writeNo findings

    Why it is in this group

    • The name "request_introduction" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Retired on 19 Oct 2026: SwapEazi collects no contact details for introductions. Calls answer RETIRED. The next step after route_intent is the chosen route's handoff_url, the provider's own sign-in or account page.

    Annotations the server declares

    • title: Retired: request an introduction
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • swapeazi_beneficiary_checkStructural check on a payment destination: an IBAN's own checksum (ISO 7064 MOD 97-10), a US ABA routing number's own checksum, a BIC's format (ISO 9362), an EVM address's EIP-55 c…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.mobileMoney.phone): what the tool writes goes there.
    Description, as the server wrote it
    Structural check on a payment destination: an IBAN's own checksum (ISO 7064 MOD 97-10), a US ABA routing number's own checksum, a BIC's format (ISO 9362), an EVM address's EIP-55 checksum, a South African universal branch code recognised against known major banks, or a SADC mobile-money number (South Africa, Zimbabwe, Malawi, Zambia) assessed for the right country code and length. Catches a mistyped or mis-keyed identifier, the single most common cause of a misdirected payment. A payment platform is several rails at once (SEPA, Fedwire/ACH, stablecoin); this assessments whichever identifiers you supply. UK sort codes and most domestic account numbers carry no public checksum and are not covered. This is NOT confirmation of payee or verification of payee: it does not confirm the name on the account, only that the identifier is internally consistent (or, for a branch code or phone number, plausible). Paid: configure this server with an Authorization Bearer key (https://swapeazi.io/pricing).

    Annotations the server declares

    • title: Assess an IBAN, BIC, US routing number, SA branch code, SADC mobile money or address before you send
    • readOnlyHint: true
    • openWorldHint: false
  • swapeazi_coverageEvery currency a payment can be measured in today, and the number of directional corridors between them.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Every currency a payment can be measured in today, and the number of directional corridors between them. Call before swapeazi_landed_cost to know whether a pair is covered. Free, no key.

    Annotations the server declares

    • title: Currencies SwapEazi can measure
    • readOnlyHint: true
    • openWorldHint: false
  • swapeazi_dex_costWhat a stablecoin swap on a DEX really cost, from its transaction hash: the sender's token out and token in, each priced as the currency it tracks (USDC, EURC, cUSD, KESm/cKES, cNG…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    What a stablecoin swap on a DEX really cost, from its transaction hash: the sender's token out and token in, each priced as the currency it tracks (USDC, EURC, cUSD, KESm/cKES, cNGN, NGNm, ZARm, GHSm, XOFm, ZARP and others), measured against the independent reference for the day with a margin of error, and signed. Chains: ethereum, base, arbitrum, optimism, polygon, celo, robinhood. Free.

    Annotations the server declares

    • title: Cost of an onchain FX swap
    • readOnlyHint: true
    • openWorldHint: true
  • swapeazi_guardrail_checkBefore money moves: every eligible route for a payment scored against your own limits (maximum LDI, maximum settlement time, regulated provider required), your quote measured if yo…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Before money moves: every eligible route for a payment scored against your own limits (maximum LDI, maximum settlement time, regulated provider required), your quote measured if you pass one, beside what banks advertise, the official business-payment average and the G20 lines. Evidence against your policy, never a recommendation. Returns a signed decision record: keep it with the payment and pass it to swapeazi_guardrail_reconcile once it settles. Paid: configure this server with an Authorization Bearer key (https://swapeazi.io/pricing).

    Annotations the server declares

    • title: Pre-trade guardrail assess
    • readOnlyHint: true
    • openWorldHint: true
  • swapeazi_guardrail_reconcileAfter money moves: the signed decision record from swapeazi_guardrail_check plus what landed (figures, or the bank's MT103 or pacs.008 text) returns a signed reconciliation.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    After money moves: the signed decision record from swapeazi_guardrail_check plus what landed (figures, or the bank's MT103 or pacs.008 text) returns a signed reconciliation. Was the quote honoured, did the payment stay inside policy, how far the market moved between approval and value date, and which part of the cost the banks in the chain took. Only amounts, dates, rates and charges are read from a message, never the parties. Paid, included in the assessment it closes.

    Annotations the server declares

    • title: Reconcile a settled payment
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • swapeazi_landed_costWhat a single cross-border payment costs, in basis points, against an independent mid-market reference: give the amount sent, the amount that landed (or a provider says will land) …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    What a single cross-border payment costs, in basis points, against an independent mid-market reference: give the amount sent, the amount that landed (or a provider says will land) and the date. Returns the Landed Drag Index with its margin of error and the evidence tier. Free, no key.

    Annotations the server declares

    • title: Landed cost of a payment
    • readOnlyHint: true
    • openWorldHint: true
  • swapeazi_verify_recordVerify that a decision or reconciliation record was issued by SwapEazi and has not been altered, and read what it says.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify that a decision or reconciliation record was issued by SwapEazi and has not been altered, and read what it says. Free and keyless, so an auditor, board or counterparty can verify a payer's records without an account.

    Annotations the server declares

    • title: Verify a SwapEazi record
    • readOnlyHint: true
    • openWorldHint: false
  • verify_release_recordVerify a SwapEazi Release Record v1, the evidence of a managed payment (or a chain of them), with no key: schema (https://swapeazi.io/schemas/release-record-v1.json), hash, chain l…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Verify a SwapEazi Release Record v1, the evidence of a managed payment (or a chain of them), with no key: schema (https://swapeazi.io/schemas/release-record-v1.json), hash, chain link and Ed25519 signature against the published key. Returns valid or invalid with each test named and the first record that breaks. Nothing sent is stored. The same verification runs offline from the spec at https://swapeazi.io/standard.

    Annotations the server declares

    • title: Verify a release record
    • readOnlyHint: true
    • openWorldHint: false
Only reads 19Show 19 read-only tools
  • analyse_payment_leakageWhere the money leaks on your current provider: total cost against the official rate in money and bps, split into FX spread and fees, and the estimated saving against the recommend…Reads text others writeNo findings

    Why it is in this group

    • The name "analyse_payment_leakage" says "analyse": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Where the money leaks on your current provider: total cost against the official rate in money and bps, split into FX spread and fees, and the estimated saving against the recommended eligible route (ESTIMATED, never realised). Needs existing_provider. One analysis (POST /api/v1/payment-analyses), the same service for every payment-intelligence tool. Every figure labelled LIVE, INDICATIVE, HISTORICAL or ESTIMATED; estimated savings are never realised. Free: shares the route-assessment allowance.

    Annotations the server declares

    • title: FX leakage on a payment
    • readOnlyHint: true
    • openWorldHint: true
  • approval_statusRead a payout the agent held for approval by approval_id: awaiting_approval while it is pending; approved with the agent_approval { id, role } to pass to record_release; rejected w…No findings

    Why it is in this group

    • The name "approval_status" says "status": a word for reading.
    Description, as the server wrote it
    Read a payout the agent held for approval by approval_id: awaiting_approval while it is pending; approved with the agent_approval { id, role } to pass to record_release; rejected with the approver's reason; or expired once its release-by date passed undecided. Each decision is signed and chained to the agent's decision record. Do not release a payout while it is awaiting approval, rejected or expired. Read-only. Needs the organisation's key; demo items (aprd_) do not.

    Annotations the server declares

    • title: Approval status
    • readOnlyHint: true
    • openWorldHint: false
  • compare_payment_providersYour current provider beside every route on record for the corridor at the same amount and against the same official rate: all-in bps, total cost, beneficiary amount, eligibility a…Reads text others writeNo findings

    Why it is in this group

    • The name "compare_payment_providers" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Your current provider beside every route on record for the corridor at the same amount and against the same official rate: all-in bps, total cost, beneficiary amount, eligibility and score, plus routes known without figures. One analysis (POST /api/v1/payment-analyses), the same service for every payment-intelligence tool. Every figure labelled LIVE, INDICATIVE, HISTORICAL or ESTIMATED; estimated savings are never realised. Free: shares the route-assessment allowance.

    Annotations the server declares

    • title: Compare payment providers for one payment
    • readOnlyHint: true
    • openWorldHint: true
  • corridor_costRead-only corridor evidence: public published rates, public posts, on-chain pool prints and user receipts, summarised by corridor and provider type (bank, fintech, card, stablecoin…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Read-only corridor evidence: public published rates, public posts, on-chain pool prints and user receipts, summarised by corridor and provider type (bank, fintech, card, stablecoin). The free answer is the summary: how many rows, the median markup percent, the date range and the evidence label (published, user receipt, public post, on-chain, user-submitted). Row-level sources are not in the free answer. They are at GET https://swapeazi.io/api/v1/corridor-evidence/rows with a paid key or x402. Does not hold or move money. A record, not a ranking.

    Annotations the server declares

    • title: Corridor cost from published evidence
    • readOnlyHint: true
    • openWorldHint: false
  • evidence_passportRead a payment case by intent_id (pi_…): its lifecycle status and who reported it, the Evidence Passport (intent, evidence with provenance and freshness, provider access and depend…No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a payment case by intent_id (pi_…): its lifecycle status and who reported it, the Evidence Passport (intent, evidence with provenance and freshness, provider access and dependencies, decision, outcome), unknowns, exceptions with owner and next action, and the timeline. Use it before acting on a payment, to see what is current, what has expired and what must happen next. Read-only: it changes nothing and moves no money. Cases opened with an organisation's key need that key.

    Annotations the server declares

    • title: Payment case and Evidence Passport
    • readOnlyHint: true
    • openWorldHint: false
  • get_corridor_capacityWhich banks, fintechs, stablecoin platforms and crypto P2P routes can carry one payment, e.g.Reads text others write1 finding

    Why it is in this group

    • The name "get_corridor_capacity" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...signs in to the provider with their own credentials. SwapEazi never touches the money: it n..."

      What this check looks for
    Description, as the server wrote it
    Which banks, fintechs, stablecoin platforms and crypto P2P routes can carry one payment, e.g. 'Pay EUR 100k to Botswana', each measured the same way: corridor served (or one leg only), can carry it (yes / no / not established, against a published per-payment limit or measured P2P depth, with the source), licence in the sending and receiving country with the register, cost against the official rate (Rate Receipt where priced; otherwise 'listed, not priced', never estimated), stated speed, on/off-ramp and stablecoin path, and the forms of money each takes (bank deposit, tokenised deposit, USDC, USDT, EURC, PYUSD...) with the chains where published and whether it cashes out in the destination currency. Public sources only, every fact with its source URL and date; alphabetical, never ranked; no provider pays to be listed. Paid per call: x402 (USDC on Base, price in the 402 body, USD 0.25) via params._meta["x402/payment"], or a paid router key as Bearer. The free top line is GET https://swapeazi.io/api/v1/capacity. Who does what: the agent may compile the intent, gather the facts, propose the route that fits the user's own weights (recommend_payment_route) and prepare the instruction with a link to the provider's own sign-in. A person approves, releases, shares account details and authorises any spend above the mandate; the user signs in to the provider with their own credentials. SwapEazi never touches the money: it never connects a wallet and never asks for a signature.

    Annotations the server declares

    • title: Corridor capacity for one payment
    • readOnlyHint: true
    • openWorldHint: true
  • get_corridor_ratesSpec v1.0 name for assess_route: the official rate for the pair and each route's all-in cost and FX figure with source, read time, freshness and evidence type, settlement and requi…Reads text others writeNo findings

    Why it is in this group

    • The name "get_corridor_rates" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Spec v1.0 name for assess_route: the official rate for the pair and each route's all-in cost and FX figure with source, read time, freshness and evidence type, settlement and requirements, under an assessment_id. Same arguments as assess_route.

    Annotations the server declares

    • title: Corridor rates and routes
    • readOnlyHint: true
    • openWorldHint: true
  • get_coverageList corridors and each route's standing: proven (a real price and at least one closed landing), priced_only, or no_live_route with a reason.Reads text others writeNo findings

    Why it is in this group

    • The name "get_coverage" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List corridors and each route's standing: proven (a real price and at least one closed landing), priced_only, or no_live_route with a reason. Includes last_priced_at, last_landed_at, landed_count and max_age_seconds. A route is never proven without a closed landing. Free callers see masked route names. Same records as GET /api/v1/coverage?view=routes.

    Annotations the server declares

    • title: Route standing for every corridor
    • readOnlyHint: true
    • openWorldHint: true
  • get_mandateRead a mandate by id (man_...) for the organisation of the router key.No findings

    Why it is in this group

    • The name "get_mandate" says "get": a word for reading.
    Description, as the server wrote it
    Read a mandate by id (man_...) for the organisation of the router key. A router key is required.

    Annotations the server declares

    • title: Read one spend mandate
    • readOnlyHint: true
    • openWorldHint: false
  • get_rate_receiptReturn a stored Rate Receipt by id (rr_...).No findings

    Why it is in this group

    • The name "get_rate_receipt" says "get": a word for reading.
    Description, as the server wrote it
    Return a stored Rate Receipt by id (rr_...). Schema swapeazi.rate_receipt.v1. Includes max_age_seconds. Free callers see a masked publisher; a router key sees the source name.

    Annotations the server declares

    • title: Read one stored Rate Receipt
    • readOnlyHint: true
    • openWorldHint: false
  • intent_statusA payment intent SwapEazi is watching (from route_intent with remember: true): today's route and what paying now, locking the rate and holding unhedged need, every day since it was…No findings

    Why it is in this group

    • The name "intent_status" says "status": a word for reading.
    Description, as the server wrote it
    A payment intent SwapEazi is watching (from route_intent with remember: true): today's route and what paying now, locking the rate and holding unhedged need, every day since it was kept, and what changed (the selected route, the cost of paying today, the payer's lock-at level, the due date). Signed. Facts only; SwapEazi moves no money.

    Annotations the server declares

    • title: Remembered intent status
    • readOnlyHint: true
    • openWorldHint: false
  • liquidity_mapShows where a payment of this size can be filled, and at what cost.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Shows where a payment of this size can be filled, and at what cost. For a currency pair (e.g. ZAR-USD, NGN-USD, KES-USD, USD-MWK) and a ticket size: each venue type (exchange order books, stablecoin pools, P2P adverts, ramps and off-ramps, OTC desks, banks) with whether the evidence read shows depth at that size, the measured slippage and landing cost at that size with a Rate Receipt, the largest size the evidence supports, or Being measured with the reason. With prefunding (amount held, days held), idle fiat prefunding and stablecoin reserves on the same evidence: cost to enter and exit at that size, the peg and exit depth from the stablecoin profiles, and the past official-rate move over the same days. Figures, not advice. Unknowns listed. SwapEazi never holds, creates or moves liquidity. Free callers see Route A, Route B; a router key shows venue names. Same as GET/POST /api/v1/liquidity.

    Annotations the server declares

    • title: Map liquidity for a currency pair at a ticket size
    • readOnlyHint: true
    • openWorldHint: true
  • list_rail_accountsKeyed.No findings

    Why it is in this group

    • The name "list_rail_accounts" says "list": a word for reading.
    Description, as the server wrote it
    Keyed. The rail accounts connected with this router key: rail, env, label, the API key's last four characters, created date and cap per payment. Never a key or a secret.

    Annotations the server declares

    • title: Your connected rail accounts
    • readOnlyHint: true
    • openWorldHint: false
  • onchain_liquidityFinds 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 E…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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, Solana, Base, BNB Chain, Arbitrum and Polygon, from keyless DEX aggregator quotes (KyberSwap, ParaSwap, Jupiter): price impact against a USD 100 quote, cost against par with gas and stated fees, and each network's published time to finality. Bridge cost and time between chains from Across, Circle CCTP and LI.FI. Each chain's network fee model (EIP-1559 base fee plus tip, BNB gas price, Solana's fixed fee plus priority fee, Tron energy; HyperEVM labelled unconfirmed) with the fee for one transfer in USD and in bps of the ticket, and its 24-hour range from stored reads. The hourly reads at USD 10k, 100k, 1m and 5m for the pair, each with its age. With destination (two-letter country), the documented facts on whether suppliers there take stablecoins directly (not established where we hold no source) and the off-ramp venues SwapEazi reads in its currency. Every figure has its source, time and a Rate Receipt; each failure keeps its reason. Figures, not advice; never ranked. The SwapEazi check never holds or moves money and never asks for a wallet signature. Same as GET/POST /api/v1/onchain-liquidity. Free within the daily allowance.

    Annotations the server declares

    • title: On-chain dollar liquidity at a ticket size
    • readOnlyHint: true
    • openWorldHint: true
  • price_routesRead public prices for a corridor at a payment size: on-chain pools, public order books and public adverts, with no partner key.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read public prices for a corridor at a payment size: on-chain pools, public order books and public adverts, with no partner key. Each figure is a route option with a Rate Receipt (schema swapeazi.rate_receipt.v1): publisher, source_type, read_at, size_priced, rate, official_rate, cost_pct, confidence, evidence_ref and status (proven, priced_only or no_live_route). max_age_seconds says when to read again. A missing figure is null with a reason. Free callers see Route A, Route B; a router key sees source names. Never executes.

    Annotations the server declares

    • title: Public prices for a corridor, each with a Rate Receipt
    • readOnlyHint: true
    • openWorldHint: true
  • private_payment_statusFor a payment prepared with private: true, give the deposit_address from its quote_proof.Reads text others writeNo findings

    Why it is in this group

    • The name "private_payment_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    For a payment prepared with private: true, give the deposit_address from its quote_proof. Returns the NEAR Intents status: PENDING_DEPOSIT, KNOWN_DEPOSIT_TX, PROCESSING, SUCCESS, REFUNDED, INCOMPLETE_DEPOSIT or FAILED, with the reason when it cannot be read. Read-only, free, no key.

    Annotations the server declares

    • title: Where a private payment stands
    • readOnlyHint: true
    • openWorldHint: true
  • release_statusTracks 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 re…No findings

    Why it is in this group

    • The name "release_status" says "status": a word for reading.
    Description, as the server wrote it
    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). With no rer_id, verifies the organisation's chain of records and returns ok or the first record where it breaks. Read-only. Needs the organisation's key.

    Annotations the server declares

    • title: Release record status
    • readOnlyHint: true
    • openWorldHint: false
  • swapeazi_route_compareThe same payment sent two to four ways (a bank wire, a payment provider, a stablecoin route through an on-ramp and an off-ramp), each measured end to end against one independent re…Reads text others writeNo findings

    Why it is in this group

    • The name "swapeazi_route_compare" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The same payment sent two to four ways (a bank wire, a payment provider, a stablecoin route through an on-ramp and an off-ramp), each measured end to end against one independent reference: what left, what landed, each route's cost with a margin of error, and the exact gap between them. The rail does not change the method. Free within the daily allowance.

    Annotations the server declares

    • title: Bank or stablecoin: compare routes
    • readOnlyHint: true
    • openWorldHint: true
  • swapeazi_rwa_compareEvery tokenised Treasury and money fund SwapEazi covers (BUIDL, BENJI, OUSG, USTB, USYC, WTGXX, USDY, Spiko, CETES), landed in the investor's own currency and hedged back: after th…Reads text others writeNo findings

    Why it is in this group

    • The name "swapeazi_rwa_compare" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Every tokenised Treasury and money fund SwapEazi covers (BUIDL, BENJI, OUSG, USTB, USYC, WTGXX, USDY, Spiko, CETES), landed in the investor's own currency and hedged back: after the fee, converting in and out at their size and the hedge carry, ranked, beside a local money fund, with a one-line verdict. Landed yields free; the working with a paid key.

    Annotations the server declares

    • title: Tokenised funds, landed in your currency
    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out18
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:22 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
57
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 57 tools that change things (2 destructive, 34 irreversible, 21 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://swapeazi.io/api/mcp: tools/list returned 76 tools to an anonymous client, including remove_rail_account (destructive), submit_payment (destructive), discover_payment (irreversible), run_payments (irreversible), approve_payment_run (irreversible) and 52 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 53 to 57
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 49 to 53

Findings

Matches of fixed checks, with the text they matched.

22 warn5 info
  • The server marks "discover_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "discover_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "payment_run_status" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_run_status" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "recommend_payment_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "recommend_payment_route" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "assess_route" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "check_fx_charges" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_fx_charges" says "charge": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "swapeazi_corridor_registry" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
Show 21 more findings
  • The server marks "payout_preflight" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payout_preflight" says "payout": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "swapeazi_forward" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "compile_intent" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "coverage" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "payout_rules" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payout_rules" says "payout": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "payment_controls" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_controls" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "check_payment_against_mandate" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_payment_against_mandate" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "rail_position" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "rate_deal_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "calculate_payment_cost" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "calculate_payment_cost" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "get_payment_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "get_payment_guide" says "get": a word for reading.

    What this check looks for
  • The server marks "check_provider_liquidity" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "request_payment_approval" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "request_payment_approval" says "request": a word for a change.

    What this check looks for
  • The server marks "track_payment_settlement" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "track_payment_settlement" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "payment_index" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "payment_index" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "tokenized_finance_intel" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...n (intent) mandate, a Verifiable Intent credential, or x402 payment requirements (accepts[..."

    What this check looks for
  • The input schema at properties.verifiable_intent.description mentions "credential".

    Matched text

    inputSchema.properties.verifiable_intent.description: "A Verifiable Intent credential: the serialised SD-JWT, or decoded mand..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...ret and a required cap per payment. The credentials are proven with a read (no payment is s..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...a connected rail account and its stored credentials. Payments already sent stay readable in..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...signs in to the provider with their own credentials. SwapEazi never touches the money: it n..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 53 -> 57.View diff
    • Tools that change things, listed without credentials: 53 to 57
  2. Tools8 added, 6 changed.+8 added~6 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 49 -> 53.View diff
    • Tools that change things, listed without credentials: 49 to 53
  4. Tools66 changed.~66 changedView diff

Install

Pinned to version 2.5.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http swapeazi https://swapeazi.io/api/mcp
claude mcp add --transport http swapeazi https://swapeazi.io/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__swapeazi__liquidity_map",
      "mcp__swapeazi__onchain_liquidity",
      "mcp__swapeazi__release_status",
      "mcp__swapeazi__swapeazi_rwa_compare",
      "mcp__swapeazi__intent_status",
      "mcp__swapeazi__private_payment_status",
      "mcp__swapeazi__evidence_passport",
      "mcp__swapeazi__approval_status",
      "mcp__swapeazi__price_routes",
      "mcp__swapeazi__get_rate_receipt",
      "mcp__swapeazi__get_coverage",
      "mcp__swapeazi__get_mandate",
      "mcp__swapeazi__list_rail_accounts",
      "mcp__swapeazi__get_corridor_rates",
      "mcp__swapeazi__compare_payment_providers",
      "mcp__swapeazi__get_corridor_capacity",
      "mcp__swapeazi__corridor_cost",
      "mcp__swapeazi__swapeazi_route_compare",
      "mcp__swapeazi__analyse_payment_leakage"
    ],
    "ask": [
      "mcp__swapeazi__discover_payment",
      "mcp__swapeazi__run_payments",
      "mcp__swapeazi__approve_payment_run",
      "mcp__swapeazi__payment_run_status",
      "mcp__swapeazi__recommend_payment_route",
      "mcp__swapeazi__assess_route",
      "mcp__swapeazi__record_landed",
      "mcp__swapeazi__reconcile_payment",
      "mcp__swapeazi__record_release",
      "mcp__swapeazi__check_fx_charges",
      "mcp__swapeazi__books_record",
      "mcp__swapeazi__swapeazi_coverage",
      "mcp__swapeazi__swapeazi_corridor_registry",
      "mcp__swapeazi__swapeazi_guardrail_check",
      "mcp__swapeazi__swapeazi_guardrail_reconcile",
      "mcp__swapeazi__swapeazi_verify_record",
      "mcp__swapeazi__verify_release_record",
      "mcp__swapeazi__swapeazi_beneficiary_check",
      "mcp__swapeazi__payout_preflight",
      "mcp__swapeazi__swapeazi_dex_cost",
      "mcp__swapeazi__swapeazi_forward",
      "mcp__swapeazi__compile_intent",
      "mcp__swapeazi__map_options",
      "mcp__swapeazi__check_constraints",
      "mcp__swapeazi__reconcile_outcome",
      "mcp__swapeazi__coverage",
      "mcp__swapeazi__payout_rules",
      "mcp__swapeazi__route_intent",
      "mcp__swapeazi__prepare_payment",
      "mcp__swapeazi__confirm_payment",
      "mcp__swapeazi__payment_controls",
      "mcp__swapeazi__request_introduction",
      "mcp__swapeazi__corridor_events",
      "mcp__swapeazi__create_mandate",
      "mcp__swapeazi__check_payment_against_mandate",
      "mcp__swapeazi__payment_intent",
      "mcp__swapeazi__decide_intent",
      "mcp__swapeazi__rail_handoff",
      "mcp__swapeazi__connect_rail_account",
      "mcp__swapeazi__join_network",
      "mcp__swapeazi__rail_position",
      "mcp__swapeazi__rate_deal_history",
      "mcp__swapeazi__parallel_signal",
      "mcp__swapeazi__calculate_payment_cost",
      "mcp__swapeazi__get_payment_guide",
      "mcp__swapeazi__check_provider_liquidity",
      "mcp__swapeazi__prepare_payment_instruction",
      "mcp__swapeazi__request_payment_approval",
      "mcp__swapeazi__track_payment_settlement",
      "mcp__swapeazi__payment_index",
      "mcp__swapeazi__add_payment_outcome",
      "mcp__swapeazi__swapeazi_landed_cost",
      "mcp__swapeazi__tokenized_finance_intel"
    ],
    "deny": [
      "mcp__swapeazi__remove_rail_account",
      "mcp__swapeazi__submit_payment"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as swapeazi. Review it before you use it.

Capability tags behind 49 rules
  • mcp__swapeazi__discover_payment untrusted-input
  • mcp__swapeazi__run_payments untrusted-input
  • mcp__swapeazi__recommend_payment_route untrusted-input
  • mcp__swapeazi__assess_route untrusted-input, outbound
  • mcp__swapeazi__liquidity_map untrusted-input
  • mcp__swapeazi__onchain_liquidity untrusted-input
  • mcp__swapeazi__record_landed untrusted-input
  • mcp__swapeazi__swapeazi_corridor_registry outbound
  • mcp__swapeazi__swapeazi_guardrail_check untrusted-input
  • mcp__swapeazi__swapeazi_guardrail_reconcile untrusted-input
  • mcp__swapeazi__swapeazi_beneficiary_check outbound
  • mcp__swapeazi__swapeazi_dex_cost untrusted-input
  • mcp__swapeazi__swapeazi_forward untrusted-input, outbound
  • mcp__swapeazi__swapeazi_rwa_compare untrusted-input
  • mcp__swapeazi__compile_intent outbound
  • mcp__swapeazi__map_options untrusted-input
  • mcp__swapeazi__coverage untrusted-input, outbound
  • mcp__swapeazi__payout_rules outbound
  • mcp__swapeazi__route_intent untrusted-input, outbound
  • mcp__swapeazi__prepare_payment untrusted-input, outbound
  • mcp__swapeazi__confirm_payment untrusted-input
  • mcp__swapeazi__private_payment_status untrusted-input
  • mcp__swapeazi__request_introduction untrusted-input
  • mcp__swapeazi__corridor_events untrusted-input
  • mcp__swapeazi__price_routes untrusted-input
  • mcp__swapeazi__get_coverage untrusted-input
  • mcp__swapeazi__check_payment_against_mandate outbound
  • mcp__swapeazi__payment_intent untrusted-input, outbound
  • mcp__swapeazi__rail_handoff untrusted-input, outbound
  • mcp__swapeazi__connect_rail_account untrusted-input
  • mcp__swapeazi__join_network untrusted-input, outbound
  • mcp__swapeazi__rail_position untrusted-input, outbound
  • mcp__swapeazi__rate_deal_history outbound
  • mcp__swapeazi__parallel_signal untrusted-input
  • mcp__swapeazi__get_corridor_rates untrusted-input
  • mcp__swapeazi__calculate_payment_cost untrusted-input
  • mcp__swapeazi__compare_payment_providers untrusted-input
  • mcp__swapeazi__get_corridor_capacity untrusted-input
  • mcp__swapeazi__get_payment_guide untrusted-input
  • mcp__swapeazi__check_provider_liquidity untrusted-input, outbound
  • mcp__swapeazi__prepare_payment_instruction untrusted-input
  • mcp__swapeazi__submit_payment untrusted-input
  • mcp__swapeazi__payment_index outbound
  • mcp__swapeazi__add_payment_outcome untrusted-input
  • mcp__swapeazi__corridor_cost untrusted-input
  • mcp__swapeazi__swapeazi_landed_cost untrusted-input
  • mcp__swapeazi__swapeazi_route_compare untrusted-input
  • mcp__swapeazi__analyse_payment_leakage untrusted-input
  • mcp__swapeazi__tokenized_finance_intel untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.MsingathiM/swapeazi/verify?hash=ffc4ad92d6d3e500e62810f6e9c1e8f9fdc9f53e6c7bfa7833f30568db4bd442" | jq -e '.changed == false'

Pinned hash ffc4ad92d6d3, from Nov 19, 2026, 10:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.MsingathiM/swapeazi/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.MsingathiM/swapeazi
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.MsingathiM/swapeazi.svg)](https://radar.anlyon.com/servers/io.github.MsingathiM/swapeazi)

Source: MCP Registry · repository. Synced Nov 19, 2026, 11:17 UTC.

SwapEazi MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SwapEazi MCP server safe?

No scan can promise that. What its definitions show: 74 tools, 55 of which can change, send or delete something, and 27 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SwapEazi MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: remove_rail_account and submit_payment.

Can the SwapEazi MCP server do things that cannot be undone?

Yes. 32 tools can send, pay, publish or merge: discover_payment, run_payments, approve_payment_run, payment_run_status, recommend_payment_route, assess_route and 26 more.

What tools does the SwapEazi MCP server have?

74 tools: 2 destructive, 32 irreversible, 21 write, 19 read. remove_rail_account, submit_payment, discover_payment, run_payments, approve_payment_run, payment_run_status, recommend_payment_route, assess_route and 66 more.

Does the SwapEazi MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SwapEazi MCP server send data to outside services?

18 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): assess_route, swapeazi_corridor_registry, swapeazi_beneficiary_check, swapeazi_forward, compile_intent, coverage and 12 more.

Has the SwapEazi MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.