MCP Request-tracker
PYPI · MCP-REQUEST-TRACKER-CRUNCHTOOLS
Secure MCP server for Request Tracker (RT) ticket management
Available components
Last scanned (22 hours ago)
Scores higher than 82% of PyPI servers
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to crunchtools/mcp-request-tracker). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-or-later).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 832 tokens (~52/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.93 functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/mcp-request-tracker-crunchtools@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | crunchtools/mcp-request-tracker |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/crunchtools/mcp-request-tracker/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 1008249530 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3fbb324a9fd48621eb7f3e300da3264911c2c610d013574d3e0a4104cd51732a |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_ticket_comment Add Ticket Comment ~47
Add a private comment/note to a ticket (not visible to requestor).
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | The comment text |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
add_time_worked Add Time Worked ~45
Add time to the time worked on a ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | yes | Additional time to add in minutes |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
complete_weekly_checklist Complete Weekly Checklist ~122
Complete a weekly checklist ticket with results. This is a workflow shortcut that: 1. Takes ownership of the ticket 2. Opens the ticket 3. Adds correspondence with checklist results 4. Adds time worked (if specified) 5. Adds a "Completed" comment 6. Resolves the ticket
| Name | Type | Req | Description |
|---|---|---|---|
| checklist_results | string | yes | The checklist completion results |
| owner | string | yes | Username taking the ticket |
| ticket_id | integer | yes | The ticket ID number |
| time_minutes | integer | – | Time spent on checklist (optional) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_ticket Create Ticket ~91
Create a new ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | – | Username to assign as owner |
| priority | integer | – | Ticket priority (0-99) |
| queue | string | yes | Queue name (e.g., 'General', 'Professional') |
| requestor | string | – | Email of the requestor |
| subject | string | yes | Ticket subject/title |
| text | string | – | Initial ticket content/description |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_my_open_tickets Get My Open Tickets ~31
Get all open tickets assigned to a user.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Username to search for |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_new_tickets Get New Tickets ~37
Get all new (unassigned) tickets, optionally filtered by queue.
| Name | Type | Req | Description |
|---|---|---|---|
| queue | string | – | Optional queue name to filter by |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ticket Get Ticket ~27
Get details of a specific ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_ticket_history Get Ticket History ~30
Get the history/changelog of a ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
open_ticket Open Ticket ~48
Open a ticket (change status from new to open), optionally taking ownership.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | – | Optional username to assign as owner |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reply_to_ticket Reply To Ticket ~44
Reply to a ticket (correspondence visible to requestor).
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The reply message |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_ticket Resolve Ticket ~44
Resolve/close a ticket, optionally adding a comment.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional comment to add before resolving |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_tickets Search Tickets ~80
Search for tickets using RT query syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Field to order by, prefix with - for descending (default: -Created) |
| query | string | yes | RT query string (e.g., "Status = 'new'", "Subject LIKE 'checklist'", "Owner = 'scott'", "Queue = 'Professional'") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_ticket_owner Set Ticket Owner ~45
Set the owner of a ticket (take/assign ticket).
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | Username of the new owner |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_ticket_status Set Ticket Status ~60
Set the status of a ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | New status (e.g., 'new', 'open', 'stalled', 'resolved', 'rejected', 'deleted') |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_time_worked Set Time Worked ~43
Set the total time worked on a ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| minutes | integer | yes | Total time worked in minutes |
| ticket_id | integer | yes | The ticket ID number |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
take_ticket Take Ticket ~38
Take ownership of a ticket and open it.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | integer | yes | The ticket ID number |
| username | string | yes | Your username |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the MCP Request-tracker server?
MCP Request-tracker runs locally as a PyPI package, launched with uvx mcp-request-tracker-crunchtools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-request-tracker-crunchtools
claude mcp add crunchtools-request-tracker -- uvx mcp-request-tracker-crunchtools
What is the MCP Request-tracker server?
MCP Request-tracker is listed in the public MCP registry as io.github.crunchtools/request-tracker. Secure MCP server for Request Tracker (RT) ticket management. This page covers its PyPI package (mcp-request-tracker-crunchtools).
Is the MCP Request-tracker server safe to use?
MCP Request-tracker scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Request-tracker server expose?
MCP Request-tracker exposes 16 tools: search_tickets, get_ticket, get_ticket_history, set_ticket_owner, set_ticket_status, and 11 more. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.
Is the MCP Request-tracker server still maintained?
MCP Request-tracker is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP Request-tracker server under?
MCP Request-tracker declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.