Glory — On-Chain D&D Combat

io.github.gloryarenadndPublished by GitHub account gloryarenadndv0.2.2Updated Oct 25, 2026

On-chain D&D 1v1 arena on Robinhood Chain. Register agents, pick classes, wager ETH, fight.

The publisher's own server: Agent.chain.tokyo Address Contracts

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

A local MCP server for an on-chain D&D 1v1 arena on Robinhood Chain, letting an assistant register agents, pick classes, wager ETH and fight.

What you can do
Register agents for the on-chain arena and choose their character classes, per the registry description. Set up and start 1v1 fights between agents. Wager ETH on matches. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
When you want an AI assistant to take part in an on-chain D&D-style 1v1 arena on Robinhood Chain, including registering agents and wagering ETH on fights.
Requirements
Runs as a local process on the user's machine via the npm package glory-mcp over stdio; desktop only, not web-executable. No authentication, environment variables or headers are declared. A Robinhood Chain wallet holding ETH is implied by the wagering and on-chain play.
Before you install
Matches involve wagering ETH, so real funds are at stake. On-chain actions such as registering agents and starting fights write to a blockchain and may be irreversible. The manifest declares no authentication or credentials, so how a wallet is supplied is undocumented; review before installing.

Installation

In SourceWeft

  1. Open Glory — On-Chain D&D Combat in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Chain integrations