# Cue (remote · cue-mcp-production.up.railway.app)

Score and improve AI prompts with Cue Free and Pro account access.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cue-mcp-production.up.railway.app`: 86/100 (this document), [markdown](https://verifymcp.io/servers/kingmonkey1-cue/cue-mcp-production.md), [page](https://verifymcp.io/servers/kingmonkey1-cue/cue-mcp-production)

## Channel facts

- Endpoint: `https://cue-mcp-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.8`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Cue MCP server?

Cue is a hosted endpoint at https://cue-mcp-production.up.railway.app/mcp, so there is nothing to install locally. 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 --transport http kingmonkey1-cue 'https://cue-mcp-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kingmonkey1-cue": {
      "url": "https://cue-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kingmonkey1-cue": {
      "type": "http",
      "url": "https://cue-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kingmonkey1-cue]
url = "https://cue-mcp-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kingmonkey1-cue": {
      "type": "remote",
      "url": "https://cue-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kingmonkey1-cue --url 'https://cue-mcp-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kingmonkey1-cue:
    url: "https://cue-mcp-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kingmonkey1-cue": {
      "Transport": "http",
      "Url": "https://cue-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kingmonkey1-cue -t streamable-http -u 'https://cue-mcp-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kingmonkey1-cue": {
      "type": "http",
      "url": "https://cue-mcp-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 86, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.53 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-03 (score 86, +1)

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

### 2026-11-01 (score 85, +1)

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

### 2026-10-30 (score 84, +1)

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

### 2026-10-27 (score 83, +1)

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

### 2026-10-25 (score 82, +1)

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

### 2026-10-23 (score 81, +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-10-21 (score 80, +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.

## MCP tools (2)

### `get_profile` (~56 tokens)

Get Cue account

Always use this tool when the user asks which Cue account is connected, which email is signed in, who they are in Cue, or what Cue plan/subscription/Free/Pro status they have. Returns the authenticated Cue profile and entitlement.

Output parameters:

- `email` (string)
- `id` (string)
- `is_pro` (boolean)
- `plan` (string)

### `improve_prompt` (~85 tokens)

Improve prompt with Cue

Always use this tool when the user asks Cue to review, score, refine, rewrite, or improve an AI prompt. Free usage limits and Cue Pro entitlement are enforced by Cue. Returns a 0–10 score, concise feedback, and one improved prompt in the same language as the input.

Input parameters:

- `prompt` (string, required): The prompt text the user wants Cue to review and improve.

Output parameters:

- `feedback` (string)
- `label` (string)
- `rewrite` (string)
- `score` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kingmonkey1-cue/cue-mcp-production#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 85
- 2026-11-01: 85
- 2026-10-31: 84
- 2026-10-30: 84
- 2026-10-29: 83
- 2026-10-28: 83
- 2026-10-27: 83
- 2026-10-26: 82
- 2026-10-25: 82
- 2026-10-24: 81
- 2026-10-23: 81
- 2026-10-22: 80
- 2026-10-21: 80
- 2026-10-20: 79
- 2026-10-19: 79

## Common questions

### What is the Cue MCP server?

Cue is an MCP server listed in the public MCP registry as io.github.KingMonkey1/cue. Score and improve AI prompts with Cue Free and Pro account access. This page covers its hosted endpoint (https://cue-mcp-production.up.railway.app/mcp).

### Is the Cue MCP server safe to use?

Cue scores 86 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 Cue MCP server expose?

Cue exposes 2 tools: get_profile, improve_prompt. Their descriptions and schemas cost roughly 141 tokens of context every time the server is loaded.

### Does the Cue MCP server require authentication?

Its publisher declares no required credentials for Cue. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Cue MCP server still maintained?

Cue is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Cue MCP server?

VerifyMCP ran 3 checks on Cue, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Cue: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://cue-mcp-production.up.railway.app/mcp
- Website: https://cue-prompt.com/
- Changelog RSS feed: https://verifymcp.io/servers/kingmonkey1-cue/cue-mcp-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/kingmonkey1-cue/cue-mcp-production/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/kingmonkey1-cue/cue-mcp-production.json
- HTML version of this page: https://verifymcp.io/servers/kingmonkey1-cue/cue-mcp-production