# io.github.CloudCorpRecords/worktrack-port (npm · @reneturcios/worktrack-port)

Jira issues and Confluence pages via the REST APIs, as MCP tools.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/worktrack-port`: 66/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-worktrack-port/reneturcios-worktrack-port.md), [page](https://verifymcp.io/servers/cloudcorprecords-worktrack-port/reneturcios-worktrack-port)
- oci · `ghcr.io/cloudcorprecords/worktrack-port`: 42/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-worktrack-port/ghcr-io-cloudcorprecords-worktrack-port.md), [page](https://verifymcp.io/servers/cloudcorprecords-worktrack-port/ghcr-io-cloudcorprecords-worktrack-port)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/worktrack-port`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 641 tokens (~53/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/worktrack-port MCP server?

io.github.CloudCorpRecords/worktrack-port runs locally as an npm package, launched with npx -y @reneturcios/worktrack-port. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-worktrack-port -- npx -y @reneturcios/worktrack-port
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-worktrack-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/worktrack-port"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-worktrack-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/worktrack-port"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-worktrack-port -- npx -y @reneturcios/worktrack-port
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-worktrack-port": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/worktrack-port"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-worktrack-port --command npx --arg -y --arg @reneturcios/worktrack-port
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-worktrack-port:
    command: "npx"
    args: ["-y", "@reneturcios/worktrack-port"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-worktrack-port": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/worktrack-port"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-worktrack-port -t stdio -c npx -a -y @reneturcios/worktrack-port
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-worktrack-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/worktrack-port"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 64)

First indexed and scored.

## MCP tools (12)

### `search_issues` (~55 tokens)

Search Jira issues with a JQL query.

Input parameters:

- `jql` (string, required): The JQL (Jira Query Language) query used to search for issues.
- `max_results` (number): Maximum number of issues to return.

### `get_issue` (~40 tokens)

Get a Jira issue by its key.

Input parameters:

- `issue_key` (string, required): The key of the Jira issue to retrieve (e.g. PROJ-123).

### `create_issue` (~99 tokens)

Create a new Jira issue in a project.

Input parameters:

- `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, required): Key of the Jira project in which to create the issue.
- `summary` (string, required): Summary (title) of the new Jira issue.

### `update_issue` (~85 tokens)

Update fields on an existing Jira issue.

Input parameters:

- `description` (string): New description text for the issue, converted to Atlassian Document Format; when omitted, the existing description is left unchanged.
- `issue_key` (string, required): The key of the Jira issue to update.
- `summary` (string): New summary for the issue; when omitted, the existing summary is left unchanged.

### `add_comment` (~54 tokens)

Add a comment to a Jira issue.

Input parameters:

- `body` (string, required): Text of the comment to add; converted to Atlassian Document Format.
- `issue_key` (string, required): The key of the Jira issue to comment on.

### `list_projects` (~16 tokens)

List all Jira projects on the site.

### `get_project` (~32 tokens)

Get a Jira project by its key.

Input parameters:

- `project_key` (string, required): The key of the Jira project to retrieve.

### `search_content` (~44 tokens)

Search Confluence content by text.

Input parameters:

- `limit` (number): Maximum number of search results to return.
- `query` (string, required): Text to search for in Confluence content.

### `get_page` (~40 tokens)

Get a Confluence page by its ID, including its storage-format body.

Input parameters:

- `page_id` (string, required): The ID of the Confluence page to retrieve.

### `create_page` (~69 tokens)

Create a new Confluence page in a space.

Input parameters:

- `content` (string, required): Body of the new page in Confluence storage format.
- `space_key` (string, required): Key of the Confluence space in which to create the page.
- `title` (string, required): Title of the new Confluence page.

### `update_page` (~90 tokens)

Update an existing Confluence page with a new version.

Input parameters:

- `content` (string, required): New body of the page in Confluence storage format.
- `page_id` (string, required): The ID of the Confluence page to update.
- `title` (string, required): New title for the Confluence page.
- `version` (number, required): Version number to assign to the updated page (the current version incremented by one).

### `list_spaces` (~17 tokens)

List all Confluence spaces on the site.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-worktrack-port/reneturcios-worktrack-port#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 66
- 2026-11-03: 65
- 2026-11-02: 65
- 2026-11-01: 64

## Common questions

### 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 npm package (@reneturcios/worktrack-port).

### Is the io.github.CloudCorpRecords/worktrack-port MCP server safe to use?

io.github.CloudCorpRecords/worktrack-port scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/worktrack-port
- Socket report: https://socket.dev/npm/package/@reneturcios/worktrack-port
- Repository: https://github.com/CloudCorpRecords/worktrack-port
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-worktrack-port/reneturcios-worktrack-port.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-worktrack-port/reneturcios-worktrack-port.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-worktrack-port/reneturcios-worktrack-port