ticket-ai-mcp@0.1.1
VERIFIED· not startedPublisher claims: "MCP server and CLI that learns what a good ticket looks like in your tracker, then measures new tickets against it. GitLab, Jira, GitHub." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
TICKET_AI_GITLAB_TOKENTICKET_AI_JIRA_TOKENConfiguration, not credentials: TICKET_AI_BASE_URL, TICKET_AI_JIRA_API, TICKET_AI_JIRA_EMAIL, TICKET_AI_MODEL, TICKET_AI_PROJECT, TICKET_AI_REPO, TICKET_AI_TICKET_LANGUAGE, TICKET_AI_TRACKER, TICKET_AI_UI_LANGUAGE, TICKET_AI_WRITER- Where it talks to
- no vendor host named in the codeAlso atlassian.net, openrouter.ai — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names atlassian.net, openrouter.ai as well as its own vendor. The guard injects TICKET_AI_GITLAB_TOKEN, TICKET_AI_JIRA_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
# to kill a run that is otherwise several minutes from finishing.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.<summary>Jira and GitHub</summary> ```bash # Jira — Cloud or self-hosted Server / Data Center. Which one you are on is # detected from the instance; you do not Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for ticket-ai-mcp@0.1.1 as of 6 h ago. This is the package itself, not its dependencies.