Home / MCP registry index / io.github.MsingathiM/swapeazi
SwapEazi
io.github.MsingathiM/swapeazi in the official MCP registry.
Endpoint https://swapeazi.io/api/mcp. Source: github.com/msingathim/swapeazi.
The registry describes it as: SwapEazi is the AI agent for managing cross-border payments.
We read its 66 tools on 2026-11-05. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http swapeazi https://swapeazi.io/api/mcp{
"mcpServers": {
"swapeazi": {
"url": "https://swapeazi.io/api/mcp"
}
}
}code --add-mcp '{"name":"swapeazi","type":"http","url":"https://swapeazi.io/api/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
discover_payment run_payments approve_payment_run payment_run_status recommend_payment_route assess_route liquidity_map onchain_liquidity record_landed reconcile_payment record_release release_status swapeazi_coverage swapeazi_corridor_registry swapeazi_guardrail_check swapeazi_guardrail_reconcile swapeazi_verify_record verify_release_record swapeazi_beneficiary_check payout_preflight swapeazi_dex_cost swapeazi_forward swapeazi_rwa_compare compile_intent map_options check_constraints reconcile_outcome coverage payout_rules route_intent intent_status prepare_payment confirm_payment private_payment_status payment_controls evidence_passport approval_status request_introduction corridor_events price_routes get_rate_receipt get_coverage create_mandate get_mandate check_payment_against_mandate payment_intent decide_intent rail_handoff connect_rail_account list_rail_accounts remove_rail_account join_network rail_position rate_deal_history parallel_signal get_corridor_rates calculate_payment_cost compare_payment_providers check_provider_liquidity prepare_payment_instruction and 6 more
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-05):
4f98ed19c55c9080. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/io-github-msingathim-swapeazi)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.