MCP servers observed by Lowdown
io.github.MsingathiM/swapeazi MCP server: daily status and tool changes
Required authentication (HTTP 401/403) on the latest check (2026-11-19) (Lowdown checks this server every 3 days). Lowdown checks without credentials, so no tools were listed. 1 of 4 checks in the last 30 days had this result. On 2026-11-16 a tool description with a URL appeared. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.MsingathiM/swapeazi
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.MsingathiM/swapeazi?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server required authentication (HTTP 401/403).
- Observed days in the last 30: 4
- Answered initialize and tools/list: 3
- Required authentication: 1
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 1 of 4 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed; tool count 69 → 73; a tool description with a URL appeared
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 68 → 69
What tools does it list?
73 tools on 2026-11-16:
add_payment_outcomeanalyse_payment_leakageapproval_statusapprove_payment_runassess_routebooks_recordcalculate_payment_costcheck_constraintscheck_fx_chargescheck_payment_against_mandatecheck_provider_liquiditycompare_payment_providerscompile_intentconfirm_paymentconnect_rail_accountcorridor_costcorridor_eventscoveragecreate_mandatedecide_intentdiscover_paymentevidence_passportget_corridor_capacityget_corridor_ratesget_coverageget_mandateget_payment_guideget_rate_receiptintent_statusjoin_networkliquidity_maplist_rail_accountsmap_optionsonchain_liquidityparallel_signalpayment_controlspayment_indexpayment_intentpayment_run_statuspayout_preflightpayout_rulesprepare_paymentprepare_payment_instructionprice_routesprivate_payment_statusrail_handoffrail_positionrate_deal_historyrecommend_payment_routereconcile_outcomereconcile_paymentrecord_landedrecord_releaserelease_statusremove_rail_accountrequest_introductionrequest_payment_approvalroute_intentrun_paymentssubmit_paymentswapeazi_beneficiary_checkswapeazi_corridor_registryswapeazi_coverageswapeazi_dex_costswapeazi_forwardswapeazi_guardrail_checkswapeazi_guardrail_reconcileswapeazi_landed_costswapeazi_route_compareswapeazi_rwa_compareswapeazi_verify_recordtrack_payment_settlementverify_release_record
MCP Registry declaration
- Registry name:
io.github.MsingathiM/swapeazi - Declared version: 2.4.2
- Status: active
- Declared hosts:
swapeazi.io
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.MsingathiM/swapeazi", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.MsingathiM/swapeazi?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).