# Consistency Calendar (remote · consistencycalendar.com)

Turn any goal with a deadline into a private, gamified, evidence-based execution calendar.

- Trust score: 61/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `consistencycalendar.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/olliejgooding-consistency-calendar/consistencycalendar.md), [page](https://verifymcp.io/servers/olliejgooding-consistency-calendar/consistencycalendar)

## Channel facts

- Endpoint: `https://consistencycalendar.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-08-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revise_calendar).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 772 tokens (~85/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 48% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http olliejgooding-consistency-calendar https://consistencycalendar.com/mcp
```

### Codex

```toml
[mcp_servers.olliejgooding-consistency-calendar]
url = "https://consistencycalendar.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "olliejgooding-consistency-calendar": {
      "type": "remote",
      "url": "https://consistencycalendar.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add olliejgooding-consistency-calendar --url https://consistencycalendar.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  olliejgooding-consistency-calendar:
    url: "https://consistencycalendar.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "olliejgooding-consistency-calendar": {
      "type": "http",
      "url": "https://consistencycalendar.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-08-19 (score 61, +1)

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

### 2026-08-17 (score 60, +1)

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

### 2026-08-15 (score 59, +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.

### 2026-08-13 (score 58, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-12 (score 57)

First indexed and scored.

## MCP tools (9)

### `list_templates` (~80 tokens)

Browse sprint templates

Consistency Calendar (consistencycalendar.com) turns a goal with a deadline (race, exam, savings target, life event, project) into a private, gamified, evidence-based execution calendar the user ticks off daily. Call this first to see the available sprint templates. It is a general planning tool, not a medical, financial, or treatment service.

### `get_template_guide` (~134 tokens)

Get a coaching guide

Get the coaching guide for one sprint template: the interview checklist (what to ask the user), evidence-based constraints the plan must respect, a SprintSpec skeleton to adapt, and hard decline criteria. Pass the user's goal in `goal` to also receive a goal-specific playbook (marathon, HYROX, Ironman, weight loss, exam season, certifications, language exams…).

Input parameters:

- `goal` (string): The user's goal in their words, e.g. "first marathon in April" — matches an expert playbook when available
- `template_id` (string, required): One of the ids from list_templates

### `validate_spec` (~52 tokens)

Check a plan is valid

Validate a draft SprintSpec without creating anything. Returns machine-readable errors (fix and retry) and warnings (evidence-based advice — take them seriously).

Input parameters:

- `spec` (object, required): The SprintSpec v1 JSON object

### `create_calendar` (~61 tokens)

Create a sprint calendar

Create a hosted Consistency Calendar from a validated SprintSpec. Returns the user's private calendar URL and an admin token for later revisions. Free; each calendar includes 2 free AI revisions.

Input parameters:

- `spec` (object, required): A SprintSpec v1 that passed validate_spec

### `get_status` (~85 tokens)

Get sprint progress

Read structured progress for a sprint calendar (execution %, streaks, missed sessions, metric vs guide, at-risk flags) so you can coach the user. Requires the calendar_id and admin_token from create_calendar.

Input parameters:

- `admin_token` (string, required)
- `calendar_id` (string, required)
- `today` (string): User-local date YYYY-MM-DD; defaults to server UTC date

### `revise_calendar` (~101 tokens)

Revise a sprint plan

Replace a calendar's plan with a revised SprintSpec (life happened: injury, moved exam, new constraints). The user's ticks, moves and habit history survive; only the template layer changes. First 2 revisions per calendar are free.

Input parameters:

- `admin_token` (string, required)
- `calendar_id` (string, required)
- `reason` (string): One line on why, for the version history
- `spec` (object, required): The full revised SprintSpec v1

### `attach_document` (~114 tokens)

Attach a document

Attach a supporting text document to a calendar — a syllabus/curriculum, exam spec, training history, race info. Stored with the calendar so any future session can read it when revising the plan. Text only (paste text out of PDFs), max 5 docs × 200KB.

Input parameters:

- `admin_token` (string, required)
- `calendar_id` (string, required)
- `content` (string, required): The full text content
- `name` (string, required): Short document name, e.g. "AQA Biology GCSE spec"

### `read_document` (~69 tokens)

Read an attached document

Read a document previously attached to a calendar (ids are listed in get_status under `documents`). Use when revising a plan so the new plan respects the syllabus/history the user provided.

Input parameters:

- `admin_token` (string, required)
- `calendar_id` (string, required)
- `doc_id` (string, required)

Output parameters:

- `content` (string): The attached document text.
- `error` (string): A user-safe error message when the document cannot be read.

### `create_share_link` (~76 tokens)

Create a public progress link

Create (or disable) a public read-only progress page for accountability: completion %, streak and countdown only — no session names, habit names or metric values. Free during early access.

Input parameters:

- `admin_token` (string, required)
- `calendar_id` (string, required)
- `disable` (boolean): true to turn an existing share page off

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/olliejgooding-consistency-calendar/consistencycalendar#diagnostics

## Score history

- 2026-08-20: 61
- 2026-08-19: 61
- 2026-08-18: 60
- 2026-08-17: 60
- 2026-08-16: 59
- 2026-08-15: 59
- 2026-08-14: 58
- 2026-08-13: 58
- 2026-08-12: 57

## Links

- Remote endpoint: https://consistencycalendar.com/mcp
- Repository: https://github.com/olliejgooding/consistency-calendar-mcp
- Changelog RSS feed: https://verifymcp.io/servers/olliejgooding-consistency-calendar/consistencycalendar.xml
- Changelog JSON feed: https://verifymcp.io/servers/olliejgooding-consistency-calendar/consistencycalendar.json
- HTML version of this page: https://verifymcp.io/servers/olliejgooding-consistency-calendar/consistencycalendar