SwapEazi

MCP server · hosted · v2.4.1 · io.github.msingathim/swapeazi

Online · tested 2h agoNEW · 3h agoSeen in the registry 2h ago

SwapEazi is the AI agent for managing cross-border payments.

What it does

SwapEazi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: payments. That makes it a candidate for tasks such as detect fraudulent transactions or reconcile payments.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 66 tools

Version2.4.1

PriceNot in the registry

First seen05 Nov 2026

Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

https://swapeazi.io/api/mcp streamable-http

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

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "swapeazi": {
      "url": "https://swapeazi.io/api/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE SwapEazi answered an MCP connection on 05 Nov 2026 and introduced itself as swapeazi 2.4.1 (MCP protocol 2025-06-18).

66 tools offered to AI assistants

swapeazi_landed_cost · 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
swapeazi_coverage · 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.
swapeazi_corridor_registry · 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.
swapeazi_guardrail_check · 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 busine
swapeazi_guardrail_reconcile · 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 fa
swapeazi_verify_record · 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.
verify_release_record · 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
swapeazi_beneficiary_check · 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 ag
payout_preflight · 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 Englis
swapeazi_dex_cost · 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 agains
swapeazi_route_compare · 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 ma
swapeazi_forward · 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 q

Show 54 more

swapeazi_rwa_compare · 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 car
compile_intent · 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 J
map_options · 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 clas
check_constraints · 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, v
reconcile_outcome · 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
coverage · 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
payout_rules · 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
route_intent · 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 spe
intent_status · 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 pay
record_landed · Close a remembered intent once the money arrived: 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 i
record_release · At the moment a material payment is released, record it against the organisation's release policy: 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 wit
release_status · Read a 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 rec
prepare_payment · 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 recipi
confirm_payment · 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 s
private_payment_status · 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
payment_controls · 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 prepare
evidence_passport · 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
approval_status · 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 da
discover_payment · Call this before initiating any cross-border or cross-currency payment. One call: a payment requirement in, a signed DiscoveryReport (a Decision Brief) out, across bank, PSP and stablecoin rails side by side — each leg's cost in basis point
request_introduction · 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.
corridor_events · 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 re
assess_route · Before a business commits to a cross-border payment, assess the corridor 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,
run_payments · The Payment Run. 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), asse
payment_run_status · Read a payment 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
approve_payment_run · Records the approval of a named 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
price_routes · 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, re
get_rate_receipt · 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.
reconcile_payment · Record what landed for released payments in a run: 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
get_coverage · 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
create_mandate · 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 requir
get_mandate · Read a mandate by id (man_...) for the organisation of the router key. A router key is required.
check_payment_against_mandate · 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
payment_intent · 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
decide_intent · 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.
rail_handoff · 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
connect_rail_account · 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 porta
list_rail_accounts · 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.
remove_rail_account · Keyed. Deletes a connected rail account and its stored credentials. Payments already sent stay readable in the business's own rail account.
join_network · 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.
rail_position · 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.
rate_deal_history · 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 b
liquidity_map · 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
onchain_liquidity · Where dollars are on-chain at your size: 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
parallel_signal · 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, i
get_corridor_rates · 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_ro
calculate_payment_cost · 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 rou
compare_payment_providers · 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 (P
analyse_payment_leakage · 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 existin
recommend_payment_route · Hard eligibility first (complete cost, not stale, settles by the due date, licence active, not excluded by route health), then configurable scoring (total cost, speed, reliability, liquidity, compliance), and the recommendation with why, al
check_provider_liquidity · 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.
prepare_payment_instruction · 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
request_payment_approval · 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_
submit_payment · 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
track_payment_settlement · 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 r

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Tasks it helps with

Share of each task's required capabilities it covers

Detect fraudulent transactions Payments	50%
Reconcile payments Payments	33%
Buy products online Payments	33%
Handle refund requests Payments	33%

Similar tools

Listed for the same task: detect fraudulent transactions

RevinhoREMOTELOCAL
Read-only SaaS business intelligence from GA4, Stripe, and Google Search Console
mcpREMOTELOCAL
Pay-per-query x402 business intelligence on Base, settled in USDC via the native 402 payment flow
keryxREMOTELOCAL
Autonomous research agent that pays every source it cites in USDC on Arc via x402 micropayments
ai tag debuggerREMOTELOCAL
QA-tests your site analytics, ad and consent tags (GA4, GTM, Ads, Meta, TikTok) from chat
x402 Pay — USDC API Payment HelperREMOTELOCAL
Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status
SCRIPTMASTERLABS — x402 GatewayREMOTELOCAL
OMNIGATE facilitator: settled 14 fleet services end-to-end 2026-11-02 (SELF-PROOF). Receipts public

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:

Digits86
$65/mo · Prices & score →
Ramp (AI agents)86
$15/mo · free plan · Prices & score →
Cal.com74
$12/mo · free plan · Prices & score →
Tipalti67
$99/mo · Prices & score →

All AI agents to detect fraudulent transactions, ranked →

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://swapeazi.io/api/mcp	DECLARED	SRC-001 Official MCP Registry	2h ago
Local install (package)	no	DECLARED	SRC-001 Official MCP Registry	2h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	2h ago
Website	https://swapeazi.io	DECLARED	SRC-001 Official MCP Registry	2h ago
Repository	https://github.com/msingathim/swapeazi	DECLARED	SRC-001 Official MCP Registry	2h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	2h ago
Version	2.4.1	DECLARED	SRC-001 Official MCP Registry	2h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	2h ago

Change history

NEW05 Nov 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is SwapEazi still online?

Free alerts · no account▲ 0

Do you run SwapEazi? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor SwapEaziLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about SwapEazi

How do I connect SwapEazi?

Use the hosted endpoint https://swapeazi.io/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does SwapEazi offer?

When Electra Index connected on 05 Nov 2026, it listed 66 tools: swapeazi_landed_cost, swapeazi_coverage, swapeazi_corridor_registry, swapeazi_guardrail_check, swapeazi_guardrail_reconcile, swapeazi_verify_record, verify_release_record, swapeazi_beneficiary_check and more. The full list is in "Live check" above.

Is SwapEazi online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.

What can I use SwapEazi for?

Based on its description, it is most relevant to: detect fraudulent transactions, reconcile payments, buy products online, handle refund requests.