MCP servers observed by Lowdown
exchange.merx/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 66 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; 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:exchange.merx/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:exchange.merx/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
66 tools on 2026-11-17:
agent_statusanalyze_pricesapprove_trc20calculate_savingscall_contractcancel_monitorcancel_standing_ordercheck_address_resourcescompare_providerscompile_policyconvert_addresscreate_accountcreate_invoicecreate_monitorcreate_ordercreate_paid_ordercreate_standing_orderdeposit_trxenable_auto_depositensure_resourcesestimate_contract_callestimate_transaction_costexecute_intentexecute_swapexplain_conceptget_account_infoget_balanceget_best_priceget_blockget_chain_parametersget_contract_infoget_deposit_infoget_orderget_price_historyget_pricesget_standing_orderget_swap_quoteget_token_infoget_token_priceget_transactionget_transaction_historyget_trc20_balanceget_trx_balanceget_trx_pricelist_monitorslist_orderslist_providerslist_standing_ordersloginlookup_invoicepay_invoiceread_contractregister_agentrequest_paymentresource_broadcastsearch_transaction_historyset_api_keyset_private_keysimulatesuggest_durationtransfer_trc20transfer_trxvalidate_addresswait_for_delegationwatch_addresswithdraw
MCP Registry declaration
- Registry name:
exchange.merx/mcp - Declared version: 1.0.5
- Status: active
- Declared hosts:
merx.exchange
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:exchange.merx/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:exchange.merx/mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:exchange.merx/mcp -- npx -y merx-mcp
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).