io.github.CloudCorpRecords/worktrack-port
OCI · GHCR.IO/CLOUDCORPRECORDS/WORKTRACK-PORT · 2 COMPONENTS
Jira issues and Confluence pages via the REST APIs, as MCP tools.
Available components
Last scanned (9 hours ago)
Scores higher than 53% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 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 641 tokens (~53/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 40
First indexed and scored.
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 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/worktrack-port@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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_comment ~54
Add a comment to a Jira issue.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Text of the comment to add; converted to Atlassian Document Format. |
| issue_key | string | yes | The key of the Jira issue to comment on. |
No output schema declared.
No examples provided.
create_issue ~99
Create a new Jira issue in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description text for the new issue; converted to Atlassian Document Format. |
| issue_type | string | – | Issue type name for the new issue (e.g. Task); defaults to Task when omitted. |
| project_key | string | yes | Key of the Jira project in which to create the issue. |
| summary | string | yes | Summary (title) of the new Jira issue. |
No output schema declared.
No examples provided.
create_page ~69
Create a new Confluence page in a space.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Body of the new page in Confluence storage format. |
| space_key | string | yes | Key of the Confluence space in which to create the page. |
| title | string | yes | Title of the new Confluence page. |
No output schema declared.
No examples provided.
get_issue ~40
Get a Jira issue by its key.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_key | string | yes | The key of the Jira issue to retrieve (e.g. PROJ-123). |
No output schema declared.
No examples provided.
get_page ~40
Get a Confluence page by its ID, including its storage-format body.
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | string | yes | The ID of the Confluence page to retrieve. |
No output schema declared.
No examples provided.
get_project ~32
Get a Jira project by its key.
| Name | Type | Req | Description |
|---|---|---|---|
| project_key | string | yes | The key of the Jira project to retrieve. |
No output schema declared.
No examples provided.
list_projects ~16
List all Jira projects on the site.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_spaces ~17
List all Confluence spaces on the site.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_content ~44
Search Confluence content by text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of search results to return. |
| query | string | yes | Text to search for in Confluence content. |
No output schema declared.
No examples provided.
search_issues ~55
Search Jira issues with a JQL query.
| Name | Type | Req | Description |
|---|---|---|---|
| jql | string | yes | The JQL (Jira Query Language) query used to search for issues. |
| max_results | number | – | Maximum number of issues to return. |
No output schema declared.
No examples provided.
update_issue ~85
Update fields on an existing Jira issue.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description text for the issue, converted to Atlassian Document Format; when omitted, the existing description is left unchanged. |
| issue_key | string | yes | The key of the Jira issue to update. |
| summary | string | – | New summary for the issue; when omitted, the existing summary is left unchanged. |
No output schema declared.
No examples provided.
update_page ~90
Update an existing Confluence page with a new version.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | New body of the page in Confluence storage format. |
| page_id | string | yes | The ID of the Confluence page to update. |
| title | string | yes | New title for the Confluence page. |
| version | number | yes | Version number to assign to the updated page (the current version incremented by one). |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/worktrack-port MCP server?
io.github.CloudCorpRecords/worktrack-port runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/worktrack-port:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/worktrack-port
claude mcp add cloudcorprecords-worktrack-port -- docker run --rm -i ghcr.io/cloudcorprecords/worktrack-port:0.1.0
What is the io.github.CloudCorpRecords/worktrack-port MCP server?
io.github.CloudCorpRecords/worktrack-port is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/worktrack-port. Jira issues and Confluence pages via the REST APIs, as MCP tools. This page covers its container image (ghcr.io/cloudcorprecords/worktrack-port).
Is the io.github.CloudCorpRecords/worktrack-port MCP server safe to use?
io.github.CloudCorpRecords/worktrack-port scores 42 out of 100 on VerifyMCP. 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 io.github.CloudCorpRecords/worktrack-port MCP server expose?
io.github.CloudCorpRecords/worktrack-port exposes 12 tools: search_issues, get_issue, create_issue, update_issue, add_comment, and 7 more. Their descriptions and schemas cost roughly 641 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/worktrack-port MCP server still maintained?
io.github.CloudCorpRecords/worktrack-port is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.CloudCorpRecords/worktrack-port MCP server under?
io.github.CloudCorpRecords/worktrack-port declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.