Burn-to-create looksmaxxing engine on MegaETH. 14 MCP tools for DeFi, NFTs, and burns.
MegaChad is a Model Context Protocol (MCP) server and burn-to-create looksmaxxing engine on MegaETH. It exposes 20 MCP tools that let AI agents interact with DeFi, NFTs, identity, and cross-chain operations on the MegaETH real-time blockchain. Endpoint: (Streamable HTTP) Connect any MCP-compatible client (Claude Desktop, Cursor, etc.): ------|-------------| | Token supply, circulating supply,…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
The repository archive could not be read at scan time (The operation was aborted due to timeout), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.
MegaChad is a Model Context Protocol (MCP) server and burn-to-create looksmaxxing engine on MegaETH. It exposes 20 MCP tools that let AI agents interact with DeFi, NFTs, identity, and cross-chain operations on the MegaETH real-time blockchain. Endpoint: (Streamable HTTP) Connect any MCP-compatible client (Claude Desktop, Cursor, etc.): ------|-------------| | Token supply, circulating supply, burn count | | $MEGACHAD price in ETH from Kumbaya DEX | | Swap quote for ETH → $MEGACHAD with calldata…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.