ui-ticket-mcp
PYPI · UI-TICKET-MCP
Human-to-AI code review bridge. Review UI in the browser, AI agents fix code via MCP.
Available components
Last scanned (23 hours ago)
Scores higher than 70% of PyPI servers
Category Testing and QA
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (CC-BY-NC-4.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 586 tokens (~53/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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.
- 3 Nov 26 +10
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.63 functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
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/ui-ticket-mcp@1.6.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| No linked repository | 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_review ~90
Add a new review comment to a page. Optional metadata is a JSON string with element annotation context. Tag can be: bug, suggestion, question, general. Set parent_id to reply to an existing review.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | yes | – |
| metadata | – | – | – |
| page_id | string | yes | – |
| parent_id | – | – | – |
| tag | string | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
batch_resolve ~60
Resolve all open reviews on a page. Use only after all reviews on the page have been addressed. Verify changes are scoped to this page and don't affect other pages unintentionally.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | – |
| resolved_by | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_github_issue ~74
Create a GitHub issue on the ui-ticket-mcp repository using the gh CLI. Requires gh to be installed and authenticated (https://cli.github.com). Label must be either 'bug' or 'enhancement'.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| label | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
find_source_file_tool ~71
Find source files in PROJECT_ROOT that match a page_id. Use this to locate the page-specific source file before making changes. If multiple files match, prefer the page-specific file over shared/common components. Only modify shared components if the user explicitly requests a global change.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_annotated_reviews ~82
Get only reviews that have element annotation metadata. Shows full element context for targeted fixes. Use this to understand exactly which element the reviewer pointed at — includes selector, fingerprint (tag, column, text, role), source context (component > section), accessibility info, and styles. This context helps you make precise, scoped changes.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_pending_work ~57
Get all open reviews grouped by page. Ready-to-work list for agents. Each review is scoped to a page_id — your fixes should target that specific page only. If a review is ambiguous, ask the user for clarification before making changes.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_review_summary ~22
Get a summary of all pages with open/resolved review counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_reviews ~24
Get review comments, optionally filtered by page_id.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_setup_guide ~30
Get the full setup guide for the review system (MCP server + REST API + browser UI).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
reopen_review ~23
Reopen a previously resolved review.
| Name | Type | Req | Description |
|---|---|---|---|
| review_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_review ~53
Mark a review as resolved. Only resolve after verifying your changes are scoped correctly — page-specific reviews should not cause global side effects on other pages.
| Name | Type | Req | Description |
|---|---|---|---|
| resolved_by | string | – | – |
| review_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the ui-ticket-mcp server?
ui-ticket-mcp runs locally as a PyPI package, launched with uvx ui-ticket-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ui-ticket-mcp
claude mcp add 0ics-srls-ui-ticket-mcp -- uvx ui-ticket-mcp
What is the ui-ticket-mcp server?
ui-ticket-mcp is listed in the public MCP registry as io.github.0ics-srls/ui-ticket-mcp. Human-to-AI code review bridge. Review UI in the browser, AI agents fix code via MCP. This page covers its PyPI package (ui-ticket-mcp).
Is the ui-ticket-mcp server safe to use?
ui-ticket-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 ui-ticket-mcp server expose?
ui-ticket-mcp exposes 11 tools: get_review_summary, get_reviews, add_review, resolve_review, reopen_review, and 6 more. Their descriptions and schemas cost roughly 586 tokens of context every time the server is loaded.
Is the ui-ticket-mcp server still maintained?
ui-ticket-mcp 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 ui-ticket-mcp server under?
ui-ticket-mcp declares the CC-BY-NC-4.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.