Skip to main content
Glama

Swarm0x

by sh.swarm0x
OverviewDiscussionsAdmin

Server Details

Run before you buy on Robinhood Chain: a simulated buy and sell, plus trades your own wallet signs.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
6.0% over 25 days
Last Tested
Transport
Streamable HTTP
URL
Repository
swarm0xsh/swarm0x-mcp
GitHub Stars
0

TDQS

A3.6/5.0

Scored across 37 tools

Disambiguation4/5

Each tool names a distinct question it answers, and the descriptions are explicit enough to separate checking a token from simulating a transaction or preparing a buy. Some overlap remains in the holder and market-momentum tools (launch_bundle, token_holders, smart_money; moving_now, graduating_soon, signals), where one tool is nearly a subset of another.

Naming Consistency4/5

Names are consistently snake_case, and actions follow a clear verb_noun style (create_rule, delete_rule, follow_wallet, prepare_buy). The pattern deviates with noun-only resource names like chain_vitals, inbox, and winners, but these are still readable and predictable.

Tool Count2/5

37 tools is well beyond the 25+ threshold, even though the server covers a broad DeFi intelligence domain. The count feels heavy, and several tools could be consolidated without losing clarity.

Completeness4/5

The surface covers chain status, token checks, holder and wallet analytics, simulation, practice trading, transaction preparation, rules, and notifications, so main workflows have no dead ends. Minor gaps remain: no update_rule, no channel setup for telegram or discord beyond a webhook, and no dedicated list of followed wallets.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedstock_prices
  2. 36 tool updates
    • First observedchain_vitals
    • First observedcheck_token
    • First observedcreate_rule
    • First observeddelete_rule
    • First observedexplain_transaction
    • First observedfollow_wallet
    • First observedgraduating_soon
    • First observedinbox
    • First observedlaunch_bundle
    • First observedleague
    • First observedlinked_wallets
    • First observedlist_channels
    • First observedlist_rules
    • First observedlook_up
    • First observedmark_as_agent
    • First observedmoving_now
    • First observedmy_bag
    • First observedmy_mite
    • First observedpractice_account
    • First observedpractice_buy
    • First observedpractice_sell
    • First observedpractice_trades
    • First observedprepare_buy
    • First observedprepare_sell
    • First observedproven_calls
    • First observedremove_channel
    • First observedset_webhook
    • First observedsignals
    • First observedsimulate_transaction
    • First observedsmart_money
    • First observedtest_rule
    • First observedtoken_holders
    • First observedunfollow_wallet
    • First observedwallet_history
    • First observedwallet_names
    • First observedwinners

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources