ONE-SHOTTED Ethereum MCP

Local stdio MCP package for agent-guided token minting and ICO launches on ONE-SHOTTED Ethereum.

The agent learns the current product rules by calling get_launch_rules. The user still signs every sensitive action in Rabby or WalletConnect, and the agent never needs a seed phrase.

get_launch_rules also includes MCP-only guidance that ICO launch expects a token minted with the ONE-SHOTTED mint contract, while still allowing mint-only flows and later ICO launch.

The MCP keeps content short and human-readable, while richer optional display and error objects are returned in structuredContent for clients that want cleaner rendering.

Install in an MCP client

Published package:

{
  "mcpServers": {
    "one-shotted-eth": {
      "command": "npx",
      "args": ["-y", "one-shotted-eth-mcp"]
    }
  }
}

Local backend override for development:

{
  "mcpServers": {
    "one-shotted-eth-local": {
      "command": "npx",
      "args": ["-y", "one-shotted-eth-mcp"],
      "env": {
        "ONE_SHOTTED_API_URL": "http://127.0.0.1:3002/api"
      }
    }
  }
}

After adding the config, restart the MCP client and ask:

Call get_launch_rules from ONE-SHOTTED and tell me the limits.

If the approval page is closed, the wallet request is rejected, or the session expires, tell the agent to retry.

New in 0.3.0:

• get_launch_rules now includes explicit MCP-only icoEligibility guidance
• sale-stage tools remind the agent that live ICO launch expects a token minted with the ONE-SHOTTED mint contract
• mint-only flows remain allowed, and later ICO launch is called out explicitly for agents

Still included from 0.2.x:

• preview_sale_transaction for a no-wallet, no-session ICO preview
• structured display payloads for cleaner agent rendering
• structured error payloads instead of raw backend text
• read-only token preflight before live ICO deploy sessions
• FDV tolerance metadata around the $5M soft limit

Tool compatibility policy

one-shotted-eth-mcp follows semver for MCP tool contracts:

• removing or renaming a tool = major
• removing or renaming an input field = major
• incompatible behavior change to a required field = major
• adding optional fields or new tools = minor
• fixes and documentation updates = patch

Development

Start from source:

npm install
npm start

Run tests:

npm test

Verify the packed artifact before publish:

npm run verify:pack

Publish notes

• Never use npm publish --ignore-scripts.
• Always run npm run verify:pack immediately before npm publish.
• prepublishOnly runs the same pack verification automatically on a normal npm publish.