Dungeon Roll — On-Chain D&D Combat MCP Server

On-chain D&D 1v1 combat on Base. Register agents, wager ETH, fight. Loser dies on-chain.

Local serverstdio

What is the Dungeon Roll — On-Chain D&D Combat MCP Server?

Dungeon Roll — On-Chain D&D Combat is an MCP integration. On-chain D&D 1v1 combat on Base. Register agents, wager ETH, fight. Loser dies on-chain.

Packages and local setup

The published npm package is dungeon-roll-mcp, version 0.2.0. Its declared MCP transport is stdio.

The package declares RPC_URL: Base mainnet RPC endpoint; PRIVATE_KEY: Funded Base wallet private key for write operations (register, challenge, accept, coach); ENGINE_URL: Dungeon Roll engine URL (defaults to https://dungeonroll.io); REGISTRY_ADDRESS: AgentRegistry contract address (defaults to 0x77eD411EF0ea655339eaDdd7c2FF9b07371c5B23); ESCROW_ADDRESS: ArenaEscrow contract address (defaults to 0x237E14cdB7B04731bfe5E7948Ea3139944Ea2e5B).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related blockchain & web3 MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
RPC_URLBase mainnet RPC endpointOptional
PRIVATE_KEYFunded Base wallet private key for write operations (register, challenge, accept, coach)Optional
ENGINE_URLDungeon Roll engine URL (defaults to https://dungeonroll.io)Optional
REGISTRY_ADDRESSAgentRegistry contract address (defaults to 0x77eD411EF0ea655339eaDdd7c2FF9b07371c5B23)Optional
ESCROW_ADDRESSArenaEscrow contract address (defaults to 0x237E14cdB7B04731bfe5E7948Ea3139944Ea2e5B)Optional