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

CueAPI agent-work scheduling: cues, executions, claiming, heartbeats, and outcomes.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/cueport`
- 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**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 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 2 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 1110 tokens (~74/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cueapi_delete_cue" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 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.

**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.

## Install

### How do I install the io.github.CloudCorpRecords/cueport MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-02 (score 68)

First indexed and scored.

## MCP tools (15)

### `cueapi_create_cue` (~199 tokens)

Create a recurring (cron) or one-time (at) cue in CueAPI.

Input parameters:

- `callback_url` (string): Callback URL invoked when the cue fires.
- `default_payload` (object): Default payload object sent when the cue fires.
- `description` (string): Description of the cue.
- `method` (string): HTTP method for the callback request.
- `name` (string, required): Cue name.
- `platform` (string): Platform associated with the cue.
- `require_payload_override` (boolean): Whether firing the cue requires a payload override.
- `required_payload_keys` (array): List of payload keys required for the cue.
- `schedule` (string, required): Schedule expression, such as a cron expression for a recurring cue or an at time for a one-time cue.
- `task_name` (string): Task name associated with the cue.
- `timezone` (string): Timezone in which the schedule is evaluated, such as UTC.

### `cueapi_list_cues` (~50 tokens)

List cues, optionally filtered by status.

Input parameters:

- `limit` (integer): Maximum number of cues to return.
- `status` (string): Cue status to filter by, such as active or paused.

### `cueapi_get_cue` (~30 tokens)

Fetch details for a single cue by id.

Input parameters:

- `cue_id` (string, required): Cue identifier.

### `cueapi_fire_cue` (~89 tokens)

Fire an existing cue immediately, with an optional payload override and merge strategy (merge or replace, default merge).

Input parameters:

- `cue_id` (string, required): Cue identifier.
- `merge_strategy` (string): How the payload override combines with the default payload: merge or replace, default merge.
- `payload_override` (object): Payload object to use for this firing, overriding the cue's default payload.

### `cueapi_update_cue` (~217 tokens)

Update a cue's mutable fields (name, schedule, callback, payload, etc.). Sparse: only provided fields are sent.

Input parameters:

- `callback_url` (string): Callback URL invoked when the cue fires.
- `cue_id` (string, required): Cue identifier.
- `default_payload` (object): Default payload object sent when the cue fires.
- `description` (string): Description of the cue.
- `method` (string): HTTP method for the callback request.
- `name` (string): Cue name.
- `platform` (string): Platform associated with the cue.
- `require_payload_override` (boolean): Whether firing the cue requires a payload override.
- `required_payload_keys` (array): List of payload keys required for the cue.
- `schedule` (string): Schedule expression, such as a cron expression for a recurring cue or an at time for a one-time cue.
- `task_name` (string): Task name associated with the cue.
- `timezone` (string): Timezone in which the schedule is evaluated, such as UTC.

### `cueapi_pause_cue` (~29 tokens)

Pause a cue so it stops firing.

Input parameters:

- `cue_id` (string, required): Cue identifier.

### `cueapi_resume_cue` (~26 tokens)

Resume a paused cue.

Input parameters:

- `cue_id` (string, required): Cue identifier.

### `cueapi_delete_cue` (~26 tokens)

Delete a cue permanently.

Input parameters:

- `cue_id` (string, required): Cue identifier.

### `cueapi_list_executions` (~61 tokens)

List historical executions, optionally filtered by cue and status.

Input parameters:

- `cue_id` (string): Cue identifier to filter by.
- `limit` (integer): Maximum number of executions to return.
- `status` (string): Execution status to filter by.

### `cueapi_get_execution` (~32 tokens)

Fetch a single execution by id, with state and outcome.

Input parameters:

- `execution_id` (string, required): Execution identifier.

### `cueapi_list_claimable_executions` (~73 tokens)

List unclaimed worker executions, filtered server-side by task and agent.

Input parameters:

- `agent` (string): Agent name to filter claimable executions by.
- `limit` (integer): Maximum number of claimable executions to return.
- `task` (string): Task name to filter claimable executions by.

### `cueapi_claim_execution` (~42 tokens)

Atomically claim a specific execution for processing.

Input parameters:

- `execution_id` (string, required): Execution identifier.
- `worker_id` (string): Identifier of the claiming worker.

### `cueapi_claim_next_execution` (~52 tokens)

Claim the next available execution, optionally filtered by task name.

Input parameters:

- `task_name` (string): Task name to filter claimable executions by.
- `worker_id` (string): Identifier of the claiming worker.

### `cueapi_execution_heartbeat` (~72 tokens)

Extend the claim lease on an in-flight execution. worker_id is required and is sent via the X-Worker-Id header.

Input parameters:

- `execution_id` (string, required): Execution identifier.
- `worker_id` (string, required): Identifier of the worker holding the claim, sent via the X-Worker-Id header.

### `cueapi_report_outcome` (~112 tokens)

Report a write-once outcome for an execution, with evidence (external id, result URL, or summary).

Input parameters:

- `execution_id` (string, required): Execution identifier.
- `external_id` (string): External identifier associated with the outcome as evidence.
- `outcome` (string, required): Outcome of the execution, such as succeeded.
- `result_type` (string): Type of the execution result.
- `result_url` (string): URL of the execution result.
- `summary` (string): Summary of the execution outcome.

## Diagnostics

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

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 68

## Common questions

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

io.github.CloudCorpRecords/cueport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/cueport. CueAPI agent-work scheduling: cues, executions, claiming, heartbeats, and outcomes. This page covers its npm package (@reneturcios/cueport).

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

io.github.CloudCorpRecords/cueport scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting 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/cueport MCP server expose?

io.github.CloudCorpRecords/cueport exposes 15 tools: cueapi_create_cue, cueapi_list_cues, cueapi_get_cue, cueapi_fire_cue, cueapi_update_cue, and 10 more. Their descriptions and schemas cost roughly 1,110 tokens of context every time the server is loaded.

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

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

io.github.CloudCorpRecords/cueport 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/cueport
- Socket report: https://socket.dev/npm/package/@reneturcios/cueport
- Repository: https://github.com/CloudCorpRecords/cueport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-cueport/reneturcios-cueport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-cueport/reneturcios-cueport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-cueport/reneturcios-cueport