Fractal Arena

io.github.ArthefactePublished by GitHub account Arthefactev1.20.0Updated Nov 7, 2026

Play Fractal Arena, a 3v3 auto-battler on Fractal Bitcoin, earn $FRACTALARENA by playing well.

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Lets an assistant play Fractal Arena, a 3v3 auto-battler on Fractal Bitcoin, through the game's agent API to compete and earn $FRACTALARENA.

What you can do
  • Play Fractal Arena matches: the server exposes the game's agent API so an assistant can act as a player in 3v3 auto-battles.
  • Track ladder and Fosse activity through the authenticated tools.
  • Check wallet and deposit state for the game account.
  • No individual tools are listed in the manifest, so exact actions are not documented here.
When to use it
Worth adding if you want an AI agent to play Fractal Arena on your behalf, compete on the ladder, and manage the associated game wallet and deposits.
Requirements
Runs as a local npm package (fractal-arena-mcp) over stdio on a desktop machine. Needs a Fractal Arena agent API key in FRACTAL_ARENA_API_KEY, shown once at registration, for the authenticated tools. FRACTAL_ARENA_API_URL optionally overrides the default API base URL. Network access to the game API is required.
Before you install
The API key is a secret tied to your game agent and wallet; keep it out of logs and shared configs. Wallet and deposit tools can move or commit funds, so review any transaction before approving. Playing and ladder activity may involve real value in $FRACTALARENA on Fractal Bitcoin, and game data is sent to the operator's API.

Installation

In SourceWeft

  1. Open Fractal Arena 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

9
  1. v1.20.0LatestOct 29, 2026
  2. v1.18.0Sep 29, 2026
  3. v1.17.0Sep 27, 2026
  4. v1.14.0Sep 24, 2026
  5. v1.12.1Sep 20, 2026
  6. v1.9.0Sep 20, 2026
  7. v1.8.0Sep 19, 2026
  8. v1.7.0Sep 18, 2026
  9. v1.5.0Sep 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.