io.github.CloudCorpRecords/cueport
OCI · GHCR.IO/CLOUDCORPRECORDS/CUEPORT · 2 COMPONENTS
CueAPI agent-work scheduling: cues, executions, claiming, heartbeats, and outcomes.
Available components
Last scanned (4 hours ago)
Scores higher than 41% of OCI servers
Category Workflow Automation
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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1110 tokens (~74/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 15 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 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.
- 3 Nov 26 +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.
- 2 Nov 26 38
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/cueport@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 →
cueapi_claim_execution ~42
Atomically claim a specific execution for processing.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Execution identifier. |
| worker_id | string | – | Identifier of the claiming worker. |
No output schema declared.
No examples provided.
cueapi_claim_next_execution ~52
Claim the next available execution, optionally filtered by task name.
| Name | Type | Req | Description |
|---|---|---|---|
| task_name | string | – | Task name to filter claimable executions by. |
| worker_id | string | – | Identifier of the claiming worker. |
No output schema declared.
No examples provided.
cueapi_create_cue ~199
Create a recurring (cron) or one-time (at) cue in CueAPI.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
cueapi_delete_cue ~26
Delete a cue permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| cue_id | string | yes | Cue identifier. |
No output schema declared.
No examples provided.
cueapi_execution_heartbeat ~72
Extend the claim lease on an in-flight execution. worker_id is required and is sent via the X-Worker-Id header.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Execution identifier. |
| worker_id | string | yes | Identifier of the worker holding the claim, sent via the X-Worker-Id header. |
No output schema declared.
No examples provided.
cueapi_fire_cue ~89
Fire an existing cue immediately, with an optional payload override and merge strategy (merge or replace, default merge).
| Name | Type | Req | Description |
|---|---|---|---|
| cue_id | string | yes | 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. |
No output schema declared.
No examples provided.
cueapi_get_cue ~30
Fetch details for a single cue by id.
| Name | Type | Req | Description |
|---|---|---|---|
| cue_id | string | yes | Cue identifier. |
No output schema declared.
No examples provided.
cueapi_get_execution ~32
Fetch a single execution by id, with state and outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Execution identifier. |
No output schema declared.
No examples provided.
cueapi_list_claimable_executions ~73
List unclaimed worker executions, filtered server-side by task and agent.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
cueapi_list_cues ~50
List cues, optionally filtered by status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of cues to return. |
| status | string | – | Cue status to filter by, such as active or paused. |
No output schema declared.
No examples provided.
cueapi_list_executions ~61
List historical executions, optionally filtered by cue and status.
| Name | Type | Req | Description |
|---|---|---|---|
| cue_id | string | – | Cue identifier to filter by. |
| limit | integer | – | Maximum number of executions to return. |
| status | string | – | Execution status to filter by. |
No output schema declared.
No examples provided.
cueapi_pause_cue ~29
Pause a cue so it stops firing.
| Name | Type | Req | Description |
|---|---|---|---|
| cue_id | string | yes | Cue identifier. |
No output schema declared.
No examples provided.
cueapi_report_outcome ~112
Report a write-once outcome for an execution, with evidence (external id, result URL, or summary).
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Execution identifier. |
| external_id | string | – | External identifier associated with the outcome as evidence. |
| outcome | string | yes | 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. |
No output schema declared.
No examples provided.
cueapi_resume_cue ~26
Resume a paused cue.
| Name | Type | Req | Description |
|---|---|---|---|
| cue_id | string | yes | Cue identifier. |
No output schema declared.
No examples provided.
cueapi_update_cue ~217
Update a cue's mutable fields (name, schedule, callback, payload, etc.). Sparse: only provided fields are sent.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | Callback URL invoked when the cue fires. |
| cue_id | string | yes | 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. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/cueport MCP server?
io.github.CloudCorpRecords/cueport runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/cueport: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/cueport
claude mcp add cloudcorprecords-cueport -- docker run --rm -i ghcr.io/cloudcorprecords/cueport:0.1.0
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 container image (ghcr.io/cloudcorprecords/cueport).
Is the io.github.CloudCorpRecords/cueport MCP server safe to use?
io.github.CloudCorpRecords/cueport scores 40 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/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.