# Cadencz (remote · api.cadencz.com)

Plan, draft, schedule and publish social posts grounded in your Website Brain.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- remote · `api.cadencz.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-cadencz-cadencz/api.md), [page](https://verifymcp.io/servers/com-cadencz-cadencz/api)

## Channel facts

- Endpoint: `https://api.cadencz.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## 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-09-30.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 447 tokens (~31/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 69/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 7% 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; "publish_now" implies "publish" 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

Cadencz is a hosted endpoint at https://api.cadencz.com/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 com-cadencz-cadencz 'https://api.cadencz.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cadencz-cadencz": {
      "url": "https://api.cadencz.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cadencz-cadencz": {
      "type": "http",
      "url": "https://api.cadencz.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cadencz-cadencz]
url = "https://api.cadencz.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cadencz-cadencz": {
      "type": "remote",
      "url": "https://api.cadencz.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cadencz-cadencz --url 'https://api.cadencz.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cadencz-cadencz:
    url: "https://api.cadencz.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cadencz-cadencz": {
      "Transport": "http",
      "Url": "https://api.cadencz.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cadencz-cadencz -t streamable-http -u 'https://api.cadencz.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cadencz-cadencz": {
      "type": "http",
      "url": "https://api.cadencz.com/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-09-30 (score 83, +1)

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

### 2026-09-28 (score 82, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 81, +1)

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

### 2026-09-25 (score 80, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 80, +1)

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

### 2026-09-22 (score 79, +1)

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

### 2026-09-20 (score 78, +1)

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

### 2026-09-18 (score 77, +1)

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

## MCP tools (14)

### `list_workspaces` (~17 tokens)

The workspaces this token can see.

### `list_channels` (~18 tokens)

Connected social accounts and whether the plan covers them.

### `list_brains` (~17 tokens)

The Website Brains in this workspace.

### `query_brain` (~46 tokens)

Retrieve product context from a Brain for a question. Defaults to the workspace's Brain when brain_id is omitted.

Input parameters:

- `brain_id` (string)
- `question` (string, required)

### `get_current_plan` (~18 tokens)

The current weekly content plan and its items.

### `get_plan_usage` (~20 tokens)

Allowance usage against the plan's caps this period.

### `list_scheduled_posts` (~26 tokens)

Posts committed to publish in the coming days.

Input parameters:

- `days` (integer)

### `get_analytics` (~24 tokens)

Engagement totals per platform over a window.

Input parameters:

- `days` (integer)

### `compose_post` (~60 tokens)

Write one platform-native post from an idea, grounded in the Brain (the workspace's, unless brain_id names another). Draws one AI generation.

Input parameters:

- `brain_id` (string)
- `idea` (string, required)
- `platform` (string)

### `plan_week` (~24 tokens)

Run Plan My Week. Each planned post draws from the shared AI-generation allowance.

### `schedule_post` (~45 tokens)

Schedule a draft variant for a moment in time.

Input parameters:

- `scheduled_at` (string, required): ISO 8601
- `timezone` (string)
- `variant_id` (string, required)

### `publish_now` (~39 tokens)

Queue a variant for immediate delivery. Irreversible; requires confirm: true.

Input parameters:

- `confirm` (boolean, required)
- `variant_id` (string, required)

### `cancel_scheduled_post` (~26 tokens)

Pull a scheduled variant back to draft.

Input parameters:

- `variant_id` (string, required)

### `approve_plan_item` (~27 tokens)

Approve a plan item into a scheduled post.

Input parameters:

- `item_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cadencz-cadencz/api#diagnostics

## Score history

- 2026-09-30: 83
- 2026-09-29: 82
- 2026-09-28: 82
- 2026-09-27: 81
- 2026-09-26: 81
- 2026-09-25: 80
- 2026-09-24: 80
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 78
- 2026-09-20: 78
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 73
- 2026-09-09: 73
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 71
- 2026-09-05: 71
- 2026-09-04: 70
- 2026-09-03: 36

## Common questions

### What is the Cadencz MCP server?

Cadencz is an MCP server listed in the public MCP registry as com.cadencz/cadencz. Plan, draft, schedule and publish social posts grounded in your Website Brain. This page covers its hosted endpoint (https://api.cadencz.com/mcp).

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

Cadencz scores 83 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 Cadencz MCP server expose?

Cadencz exposes 14 tools: list_workspaces, list_channels, list_brains, query_brain, get_current_plan, and 9 more. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.

### Does the Cadencz MCP server require authentication?

Yes. Cadencz asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Cadencz MCP server still maintained?

Cadencz is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.cadencz.com/mcp
- Authorisation metadata: https://api.cadencz.com/.well-known/oauth-protected-resource/mcp
- Website: https://cadencz.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-cadencz-cadencz/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cadencz-cadencz/api.json
- HTML version of this page: https://verifymcp.io/servers/com-cadencz-cadencz/api