mcp-registry/io.github.megachadxyz/megachad · v1.0.0
Also listed as glama/megachadxyz/megachad-mcp-server
As of 2026-10-19 20:37 UTC, the Megachadxyz Megachad MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.6% of Glimind's liveness checks.
Burn-to-create looksmaxxing engine on MegaETH. 14 MCP tools for DeFi, NFTs, and burns.
Point your MCP client at this streamable-http endpoint: https://megachad.xyz/api/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
38 of 38 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,603 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.megachadxyz%2Fmegachad/fixes
{
"name": "build_amm_add_liquidity_tx",
"description": "Build approve(MC) + approve(MG) + addLiquidity on MegaChadLP MC/MG. The pair refunds whichever side is over-supplied. LP shares returned are stake-eligible in JESTERGOONER V4.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"amountMC",
"amountMG",
"recipient"
],
"properties": {
"address": {
"type": "string",
"description": "Sender address — used to skip approve steps if allowance is sufficient"
},
"amountMC": {
"type": "string",
"description": "MEGACHAD amount in human units"
},
"amountMG": {
"type": "string",
"description": "MEGAGOONER amount in human units"
},
"recipient": {
"type": "string",
"description": "LP token recipient (0x...)"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Build Add Liquidity Transaction"
}{
"name": "build_execute_tx",
"description": "Build execute(proposalId) calldata for a Queued Jestermogger proposal past its 2-day timelock. May be payable if any action carries ETH value.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"proposalId"
],
"properties": {
"proposalId": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "Proposal ID"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Build Execute Proposal TX"
}{
"name": "build_propose_tx",
"description": "GET form returns Framemogger top-3-burner eligibility for the proposer (only top 3 can propose each week). To actually build calldata, POST your { targets[], values[], calldatas[], description } payload to /api/defi/governance/propose-tx. Use this MCP tool to quickly check eligibility before drafting.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"proposer": {
"type": "string",
"description": "Proposer wallet address (0x...) — required for eligibility check"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Build Propose TX / Check Eligibility"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.megachadxyz/megachad"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.megachadxyz/megachad"}) over MCP.
build_staking_tx ~260 tokensbuild_amm_swap_tx ~225 tokenscross_chain_looksmaxx ~222 tokensbuild_veto_tx ~206 tokensbuild_amm_add_liquidity_tx ~200 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.megachadxyz%2Fmegachad?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.megachadxyz%2Fmegachad?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.megachadxyz%2Fmegachad.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.megachadxyz%2Fmegachad.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.megachadxyz%2Fmegachad?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:80688fc0c4fba68c…, first seen 2026-10-17, included at leaf 449 of 39,172. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable defi servers · most reliable blockchain servers · most reliable other servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 20:37 UTC, the Megachadxyz Megachad MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.6% of Glimind's liveness checks.
Megachadxyz Megachad MCP server advertises 38 tools, including build_amm_add_liquidity_tx, build_amm_swap_tx, build_execute_tx, build_propose_tx, build_queue_tx.
Point your MCP client at this streamable-http endpoint: https://megachad.xyz/api/mcp
Glimind scanned all 38 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.