Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@eip7702-rescue check if 0xabc123 is 7702-delegated"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Forensic MCP + hardened delegate for recovering assets from EIP-7702-compromised wallets.
When an EOA is delegated to a sweeper via EIP-7702, you can't fund it to pay for its own recovery — the funding is swept on arrival. This tool rescues the held assets in one atomic sponsored type-4 transaction (re-delegate + transfer-out, no window for the attacker), and ships a forensic MCP that is key-free: it diagnoses, scans, and simulates recoverability for any victim address without ever holding a private key. Firing the real rescue is a deliberate, separate human step.
→ Full spec: SPEC.md · Real mainnet case (11 NFTs recovered): CASE.md
tool | what | keys |
| is an address 7702-delegated, and to what? | none (read-only) |
| which token ids does an address still hold? | none (read-only) |
| prove ids land at | none |
| emit the exact tx sequence + calldata for the real run | none (no broadcast) |
Related MCP server: Yield Agentic Hub
forge build # compile contracts/RescueDelegate.sol
node mcp/server.mjs # run the MCP server over stdioRegister mcp/server.mjs as a stdio MCP server in your client. RESCUE_RPC overrides the RPC.
RescueDelegate(address SAFE) — destination immutable at deploy. rescue(wrap, ids) can only ever
move assets to SAFE, so it's safe to leave delegated (no open-destination drain window).
A rescue job's asset_set + outcome bind to an OCP/8281 artifact_hash → recovery-escrow receipt
(faithfulness) + scope-contestation (completeness). The MCP is the observation/action front-end of
the recovery-standards family; no trusted party at any layer.
License: CC0-1.0.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Remote MCP for A2A failure replay MCP, structured receipts, audit logs, and reviewer-ready evidence.
The MCP-native bridge to ERC-8004 (on-chain agent identity/reputation/validation): resolve registrat
Crypto transaction firewall and risk tools for MCP agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/trustless-ai/eip7702-rescue'
If you have feedback or need assistance with the MCP directory API, please join our Discord server