Claim your server

Claiming proves you own the repository, and unlocks the author-declared band on your server’s page: safer-mode flags, intended scopes, recommended config, and a badge you can paste into your README.

Claiming

sha256:9a876d5917f09d8e81e3214fe356225eb9d1a97f3c52654bb4128f183756f307

cmd:sha256:9a876d5917f09d8e81e3214fe356225eb9d1a97f3c52654bb4128f183756f307

Sign in with GitHub to claim

These badges already work today — claiming adds the author band on top.

Adoption

Live count of public repos observed wiring this server up.

ax-ray Adoption badge
[![ax-ray](/badge/cmd/sha256%3A9a876d5917f09d8e81e3214fe356225eb9d1a97f3c52654bb4128f183756f307.svg?metric=adoption)](/server/cmd/sha256%3A9a876d5917f09d8e81e3214fe356225eb9d1a97f3c52654bb4128f183756f307)
Status

The band this page currently sits in — observed, never a verdict.

ax-ray Status badge
[![ax-ray](/badge/cmd/sha256%3A9a876d5917f09d8e81e3214fe356225eb9d1a97f3c52654bb4128f183756f307.svg)](/server/cmd/sha256%3A9a876d5917f09d8e81e3214fe356225eb9d1a97f3c52654bb4128f183756f307)
  1. 1

    Prove ownership

    Sign in with GitHub. You can claim any server whose repository is under your account — we match the repo owner to your GitHub login.

  2. 2

    Add context

    Declare safer-mode flags, intended scopes, and recommended config — stated intent, shown as its own band, never blended with static facts.

  3. 3

    Embed the badge

    Copy the Markdown snippet from your page into your README. Every badge links back and reflects your current signals.

Claiming is a public ownership proof, not a contribution — no data leaves your machine.