Tickr MCP Server

@k-system/tickr-mcp npm v1.62.0

Published by @k-system — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Tickr project management — 74 tools + setup CLI wizard

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (dist/cli/hooks.js)MTC-SRC-002

In the server's implementation (`dist/cli/hooks.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execSync } from "node:child_process"; import { existsSync, readFileSync, writeFileSync, mkdirSync, chmodSync } from "n

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/cli/hooks.js

Tools 71

Each tool and what it can reach — statically extracted from the published source.

  • add_commentno sensitive capability
  • add_epic_dependencyno sensitive capability
  • add_labelno sensitive capability
  • add_project_memberno sensitive capability
  • add_relationno sensitive capability
  • add_release_ticketno sensitive capability
  • apply_presetno sensitive capability
  • assign_cycleno sensitive capability
  • assign_epicno sensitive capability
  • complete_dev_taskno sensitive capability
Show 61 more tools ↓
  • create_cycleno sensitive capability
  • create_epicno sensitive capability
  • create_implementation_itemno sensitive capability
  • create_labelno sensitive capability
  • create_projectno sensitive capability
  • create_releaseno sensitive capability
  • create_statusno sensitive capability
  • create_ticketno sensitive capability
  • delete_attachmentno sensitive capability
  • delete_commentno sensitive capability
  • delete_cycleno sensitive capability
  • delete_epicno sensitive capability
  • delete_implementation_itemno sensitive capability
  • delete_labelno sensitive capability
  • delete_statusno sensitive capability
  • delete_ticketno sensitive capability
  • fail_dev_taskno sensitive capability
  • generate_release_notesno sensitive capability
  • get_boardno sensitive capability
  • get_my_tasksno sensitive capability
  • get_next_statusesno sensitive capability
  • get_projectno sensitive capability
  • get_releaseno sensitive capability
  • get_ticketno sensitive capability
  • link_commitno sensitive capability
  • list_attachmentsno sensitive capability
  • list_commentsno sensitive capability
  • list_cyclesno sensitive capability
  • list_dev_assignmentsno sensitive capability
  • list_epicsno sensitive capability
  • list_labelsno sensitive capability
  • list_project_membersno sensitive capability
  • list_projectsno sensitive capability
  • list_relationsno sensitive capability
  • list_releasesno sensitive capability
  • list_statusesno sensitive capability
  • list_ticketsno sensitive capability
  • list_transitionsno sensitive capability
  • list_workflow_presetsno sensitive capability
  • poll_dev_queueno sensitive capability
  • publish_releaseno sensitive capability
  • remove_epic_dependencyno sensitive capability
  • remove_labelno sensitive capability
  • remove_project_memberno sensitive capability
  • remove_relationno sensitive capability
  • remove_release_ticketno sensitive capability
  • search_ticketsno sensitive capability
  • triage_acceptno sensitive capability
  • triage_listno sensitive capability
  • triage_rejectno sensitive capability
  • update_commentno sensitive capability
  • update_cycleno sensitive capability
  • update_epicno sensitive capability
  • update_implementation_itemno sensitive capability
  • update_labelno sensitive capability
  • update_project_member_roleno sensitive capability
  • update_releaseno sensitive capability
  • update_statusno sensitive capability
  • update_ticketno sensitive capability
  • update_transitionsno sensitive capability
  • whoamino sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.62.0 latest A 93/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/k-system-tickr-mcp/badge.svg)](https://mcptrustchecker.com/registry/k-system-tickr-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/k-system-tickr-mcp"><img src="https://mcptrustchecker.com/registry/k-system-tickr-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/k-system-tickr-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @k-system/tickr-mcp --online

Use the free API → How scoring works

More in Business & CRM