# io.github.CloudCorpRecords/issueport (npm · @reneturcios/issueport)

Linear teams, projects, issues and comments via GraphQL, as MCP tools.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/issueport`
- 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**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 604 tokens (~50/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/issueport MCP server?

io.github.CloudCorpRecords/issueport runs locally as an npm package, launched with npx -y @reneturcios/issueport mcp. 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-issueport -- npx -y @reneturcios/issueport mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 66, +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.

### 2026-11-03 (score 65, +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.

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

First indexed and scored.

## MCP tools (12)

### `list_issues` (~67 tokens)

List Linear issues, optionally within one team.

Input parameters:

- `limit` (number): Maximum number of issues to return; defaults to 50 when omitted.
- `team_id` (string): Id of the Linear team to restrict the listed issues to; when omitted, issues from all teams are listed.

### `get_issue` (~31 tokens)

Get a Linear issue by its id.

Input parameters:

- `issue_id` (string, required): Id of the Linear issue to retrieve.

### `create_issue` (~115 tokens)

Create a new Linear issue in a team.

Input parameters:

- `assignee_id` (string): Id of the user to assign the new issue to.
- `description` (string): Description text of the new issue.
- `label_ids` (array): Ids of the labels to attach to the new issue.
- `priority` (number): Priority of the new issue, as a number.
- `team_id` (string, required): Id of the Linear team in which to create the issue.
- `title` (string, required): Title of the new issue.

### `update_issue` (~108 tokens)

Update fields of an existing Linear issue.

Input parameters:

- `assignee_id` (string): Id of the user to assign the issue to.
- `description` (string): New description text for the issue.
- `issue_id` (string, required): Id of the Linear issue to update.
- `priority` (number): New priority of the issue, as a number.
- `state_id` (string): Id of the workflow state to move the issue to.
- `title` (string): New title for the issue.

### `search_issues` (~57 tokens)

Search Linear issues by title text.

Input parameters:

- `limit` (number): Maximum number of matching issues to return; defaults to 50 when omitted.
- `query` (string, required): Text to match, case-insensitively, against issue titles.

### `list_teams` (~13 tokens)

List Linear teams.

### `get_team` (~31 tokens)

Get a Linear team by its id.

Input parameters:

- `team_id` (string, required): Id of the Linear team to retrieve.

### `list_projects` (~12 tokens)

List Linear projects.

### `create_project` (~64 tokens)

Create a new Linear project for one or more teams.

Input parameters:

- `description` (string): Description text of the new project.
- `name` (string, required): Name of the new project.
- `team_ids` (array, required): Ids of the Linear teams to associate with the new project.

### `list_comments` (~32 tokens)

List comments on a Linear issue.

Input parameters:

- `issue_id` (string, required): Id of the Linear issue whose comments are listed.

### `create_comment` (~46 tokens)

Add a comment to a Linear issue.

Input parameters:

- `body` (string, required): Text body of the comment.
- `issue_id` (string, required): Id of the Linear issue to add the comment to.

### `archive_issue` (~28 tokens)

Archive a Linear issue.

Input parameters:

- `issue_id` (string, required): Id of the Linear issue to archive.

## Diagnostics

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

## Score history

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

## Common questions

### What is the io.github.CloudCorpRecords/issueport MCP server?

io.github.CloudCorpRecords/issueport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/issueport. Linear teams, projects, issues and comments via GraphQL, as MCP tools. This page covers its npm package (@reneturcios/issueport).

### Is the io.github.CloudCorpRecords/issueport MCP server safe to use?

io.github.CloudCorpRecords/issueport 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/issueport MCP server expose?

io.github.CloudCorpRecords/issueport exposes 12 tools: list_issues, get_issue, create_issue, update_issue, search_issues, and 7 more. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/issueport MCP server still maintained?

io.github.CloudCorpRecords/issueport 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/issueport MCP server under?

io.github.CloudCorpRecords/issueport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/issueport MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/issueport, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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