Skip to main content
Glama
Sign In

MegaChad

by io.github.megachadxyz
OverviewDiscussionsAdmin

Server Details

Burn-to-create looksmaxxing engine on MegaETH. 14 MCP tools for DeFi, NFTs, and burns.

The last two health checks of this connector failed. 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
92.2% over 66 days
Last Tested
Transport
Streamable HTTP
URL
Repository
megachadxyz/mega-chad
GitHub Stars
0
Server Listing
MegaChad MCP Server
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 38 tools

Disambiguation4/5

Most tools target a distinct resource+action pair (e.g., build_propose_tx vs build_vote_tx vs build_queue_tx). A few near-overlaps exist—get_amm_quote vs get_swap_quote (different DEXes) and the three directory tools (get_agent_index, get_protocol_registry, get_megaeth_protocols)—but descriptions clearly delineate their scopes, so an agent can tell them apart with careful reading.

Naming Consistency4/5

The dominant pattern is verb_noun in snake_case (build_*, get_*, list_*, register_*), which is consistent. Minor deviations include gasless_burn_info (should be get_gasless_burn_info) and cross_chain_looksmaxx (should be build_cross_chain_looksmaxx), but these are few and the overall style remains predictable.

Tool Count2/5

38 tools is well above the 25+ threshold that indicates an oversized set. Even for a complex protocol, this many tools will overwhelm agents and increase selection error; many could be consolidated (e.g., merging quote tools or the three directory tools).

Completeness5/5

The tool set provides thorough lifecycle coverage for the MegaChad protocol: market data, trading, liquidity, staking, governance (propose/vote/queue/execute/veto), NFT looksmaxxing, identity, referrals, and safety checks. Every read has a corresponding write or actionable step, and the governance flow is fully represented.

Tool Schema Changelog

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

  1. 8 tool updates
    • Addedbuild_execute_tx
    • Addedbuild_propose_tx
    • Addedbuild_queue_tx
    • Addedbuild_veto_tx
    • Addedget_activity_feed
    • Addedget_agent_index
    • Addedget_nft_inventory
    • Addedget_protocol_safety
  2. 10 tool updates
    • Addedbuild_amm_add_liquidity_tx
    • Addedbuild_amm_swap_tx
    • Addedbuild_staking_tx
    • Addedbuild_vote_tx
    • Addedget_amm_quote
    • Addedget_emission_schedule
    • Addedget_governance_proposal
    • Addedget_protocol_registry
    • Addedget_staking_position
    • Addedlist_governance_proposals
  3. 4 tool updates
    • Addedcross_chain_looksmaxx
    • Addedget_identity
    • Addedget_megaeth_protocols
    • Addedget_portfolio
  4. 16 tool updates
    • First observedchat_with_megachad
    • First observedgasless_burn_info
    • First observedget_agent_info
    • First observedget_bridge_info
    • First observedget_chadboard
    • First observedget_gallery
    • First observedget_looksmaxx_plan
    • First observedget_looksmaxx_requirements
    • First observedget_megachad_stats
    • First observedget_nft_metadata
    • First observedget_price
    • First observedget_referral_stats
    • First observedget_swap_quote
    • First observedget_wallet_info
    • First observedregister_early_access
    • First observedregister_referral_agent

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