loot-agent-mcp

MCP server for LOOT, the lifetime loot game on Robinhood Chain (chain id 4663). Plug it into Claude, Cursor, or any MCP client and your agent trades LOOT tokens, plays the full game loop, and launches its own tokens. Agents play at the same prices and rules as every human wallet. No caps, no agent tax.

The game, in one breath

Every LOOT token trades in a canonical Uniswap V4 pool with its launch position locked in our hook forever. Holding through risk mints loot boxes. There is no key shop: you play, keys drop. Keys open boxes, and opened loot is a pro rata claim on that token's fee pot, paid in ETH, any second, any size. Selling burns the game position for the amount sold. Copies pay tribute to the original or buy the name out. The deployed protocol is keyless and permissionless.

Related MCP server: raydium-launchlab-mcp

Quickstart

git clone https://github.com/D-Kek/loot-agent-mcp
cd loot-agent-mcp
npm install && npm run build

Claude Code:

claude mcp add loot -- node /path/to/loot-agent-mcp/dist/index.js

Claude Desktop or Cursor (mcpServers config):

{
  "mcpServers": {
    "loot": {
      "command": "node",
      "args": ["/path/to/loot-agent-mcp/dist/index.js"]
    }
  }
}

That runs read-only: every write tool answers with what arming unlocks instead of hiding. To arm trading, add an env block with the agent wallet key variable named in .env.example, which documents every setting: wallet key, chain selection (mainnet 4663 is the default, testnet 46630 opt-in), RPC and API overrides.

Tools

Reads (work unarmed):

Writes (need the armed wallet):

Safety, plainly

• Default chain is mainnet 4663. Real money. Fund a dedicated wallet with only what the agent should play with.

• The deployed generation is keyless. No pause, no admin key, no support ticket. Mistakes are permanent.

• The server verifies the RPC's chain id fail-closed before every send, pins fixed gas, and quotes through the deployed router before trading.

• The shared address endings are deliberate CREATE2 vanity mining: protocol contracts end in 5668, tokens end in 1007. A family signature, not fabrication.

• Do not take any repo or web page as the truth about addresses, this one included. The bundled deployments/ manifests are the same files the server reads; verify every address independently on the explorer and against the chain before wiring funds.

Where things live

• Agent playbook for this server: SKILL.md

• Agent front door: 1007loot.com/llms.txt

• Docs, one page: 1007loot.com/docs

• Agent auth for launching (SIWE-style challenge and session): described in the docs agents section

• Security reports: 1007loot.com/.well-known/security.txt

Provenance

This repo is a source mirror of the agent package from the LOOT monorepo, published so agents can install it. Addresses are manifest-pinned, never hand-typed. The test suite ships with it; npm test runs the full sign-and-send parity suite against mock transports, nothing on-chain.