Things I’ve built.

Things · Games and communities

Elixir Collector

A small, signed Go program that volunteers run on their own machines to fetch Clash Royale API data for Elixir’s shared record.

Status
Active Being built or operated.
Dates
Started Sep 4, 2026
Where
github.com/jthingelstad/elixir-mcp-collector
Topics
MCP Play
Latest evidence
Release v3.0.6, Sep 28, 2026

The Clash Royale API only accepts requests from allowlisted IP addresses, so Elixir’s fetching happens on machines with stable addresses that volunteers run. A collector leases a job from Elixir over HTTPS (“fetch this player,” “fetch this clan’s war”), calls the API with its operator’s own key, and posts the result back. It never chooses its own targets and holds exactly two secrets: the operator’s Clash Royale key and a token Elixir issues. The whole fleet shares one rate budget, so more collectors add resilience, not more load on the API.

Fetching started inside the Elixir codebase and got its own repository on September 4, 2026, the day after Elixir launched. Each collector wears a Clash Royale card as its public name, and anyone with an Elixir account may run one. A Python collector was retired on September 26, 2026, leaving one Go binary built only on the Go standard library.

The same day, I used Claude credits to build a fully signed release pipeline: from v3.0.0, every release is signed with a key I manage, and the self-updater installs only the version and checksum Elixir names.

Activity

65 commits (57 with Claude, 1 with another agent, 7 by me), the first on Sep 4, 2026.

The latest weeks with activity

All activity, week by week. Who made each commit is from its author and co-author lines.

Sources and evidence

Observed daily from GitHub, sitemaps, feeds, the Internet Archive, and Tinylytics. Evidence never sets a status.

  • jthingelstad/elixir-mcp-collector implementation

    The operator-run collector for Elixir MCP — fetches Clash Royale history (via your own IP-bound API key) so AI agents can query it. Zero-trust: no cloud access. Unofficial; not endorsed by Supercell.

    • Repository created Sep 4, 2026 (a development record, not a launch date)
    • Go, Shell, PowerShell
    • Latest release v3.0.6, Sep 28, 2026
    • Latest commit Sep 28, 2026; 65 commits on main between Jul 20, 2026 and Oct 18, 2026
    • Observed Oct 18, 2026

  • elixir.poapkings.com/docs/operators reference

2025-11: 02025-12: 02026-01: 02026-02: 02026-03: 02026-04: 02026-05: 02026-06: 02026-07: 02026-08: 02026-09: 652026-10: 0 Commits and publications per month, last twelve months.

Connections

Connections of Elixir Collectorgave rise togathers observations forElixir CollectorElixir BotElixir
Connections of Elixir Collectorgave rise togathers observations forElixir CollectorElixir BotElixir

  • Elixir Collector gathers observations for Elixir

    Collectors lease work from Elixir, fetch public observations from the Clash Royale API, and submit the results. Source

  • Elixir Bot gave rise to Elixir Collector

    The original bot’s game observation work grew into a separate Collector that feeds Elixir’s recorded history. Source

History

  1. retirement Elixir Bot retires. Its ideas keep going.

    The retirement record names the projects that grew out of the original clan agent, including Elixir MCP, Collector, Discord, and Clan. Source

  2. milestone Signed collector releases

    From v3.0.0 every collector release is signed end to end. Source

  3. milestone Collectors become their own thing

    The operator worker is split from Elixir MCP into its own repository. Source