MCP server and CLI that learns what a good ticket looks like in your tracker, then measures new tickets against it. GitLab, Jira, GitHub.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ticket-ai-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ticket-ai         **An MCP server and CLI that measures how your team actually writes tickets, and holds new ones to that.** Not *this ticket is bad* — *31 of the 40 tickets that shipped here have an acceptance-criteria section, and this one does not.* > **No 'Akzeptanzkriterien' section.** > 31 of the 40 exemplar tickets (78%) have one. Most ticket advice is free and therefore ignored. "Add acceptance criteria", "include steps to reproduce" — everyone has heard it, nobody changed anything. A count of what already happened in your own project is harder to wave away, and it is not an opinion about tickets. **There is no model in the loop for any of that.** Learning the house style, finding related tickets and measuring a draft are counting, and run with no key and no network beyond your tracker. Writing a ticket needs a model, so that part is opt-in and which one is your choice. **[What it found when it was run against real boards →](docs/thirty-boards.md)** ## Install ```bash uv tool install ticket-ai-mcp ``` Configuration is environment variables only — a token passed as `--token` ends up i…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.