Consistency Calendar
REMOTE · CONSISTENCYCALENDAR.COM
Turn any goal with a deadline into a private, gamified, evidence-based execution calendar.
Available components
Last scanned (20 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Productivity and Notes
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revise_calendar). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 772 tokens (~85/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Aug 26 0
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 23 Oct 2026 · Probed https://consistencycalendar.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=consistencycalendar.com | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 80100f016382e91c0e457717a7e332d2 |
| SANs: consistencycalendar.com, *.consistencycalendar.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of consistencycalendar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| consistencycalendar.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://consistencycalendar.com/mcp | Verified | 200 | |
| http (plaintext) | http://consistencycalendar.com/mcp | Inconclusive | 405 |
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 →
attach_document Attach a document ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | – |
| calendar_id | string | yes | – |
| content | string | yes | The full text content |
| name | string | yes | Short document name, e.g. "AQA Biology GCSE spec" |
Structured output declared, but exposes no named fields.
No examples provided.
create_calendar Create a sprint calendar ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | object | yes | A SprintSpec v1 that passed validate_spec |
Structured output declared, but exposes no named fields.
No examples provided.
create_share_link Create a public progress link ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | – |
| calendar_id | string | yes | – |
| disable | boolean | – | true to turn an existing share page off |
Structured output declared, but exposes no named fields.
No examples provided.
get_status Get sprint progress ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | – |
| calendar_id | string | yes | – |
| today | string | – | User-local date YYYY-MM-DD; defaults to server UTC date |
Structured output declared, but exposes no named fields.
No examples provided.
get_template_guide Get a coaching guide ~134
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…).
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | The user's goal in their words, e.g. "first marathon in April" — matches an expert playbook when available |
| template_id | string | yes | One of the ids from list_templates |
Structured output declared, but exposes no named fields.
No examples provided.
list_templates Browse sprint templates ~80
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
read_document Read an attached document ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | – |
| calendar_id | string | yes | – |
| doc_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The attached document text. |
| error | string | – | A user-safe error message when the document cannot be read. |
No examples provided.
revise_calendar Revise a sprint plan ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_token | string | yes | – |
| calendar_id | string | yes | – |
| reason | string | – | One line on why, for the version history |
| spec | object | yes | The full revised SprintSpec v1 |
Structured output declared, but exposes no named fields.
No examples provided.
validate_spec Check a plan is valid ~52
Validate a draft SprintSpec without creating anything. Returns machine-readable errors (fix and retry) and warnings (evidence-based advice — take them seriously).
| Name | Type | Req | Description |
|---|---|---|---|
| spec | object | yes | The SprintSpec v1 JSON object |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Consistency Calendar MCP server?
Consistency Calendar is a hosted endpoint at https://consistencycalendar.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.
remote · consistencycalendar.com
claude mcp add --transport http olliejgooding-consistency-calendar 'https://consistencycalendar.com/mcp'
What is the Consistency Calendar MCP server?
Consistency Calendar is an MCP server listed in the public MCP registry as io.github.olliejgooding/consistency-calendar. Turn any goal with a deadline into a private, gamified, evidence-based execution calendar. This page covers its hosted endpoint (https://consistencycalendar.com/mcp).
Is the Consistency Calendar MCP server safe to use?
Consistency Calendar scores 73 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 Consistency Calendar MCP server expose?
Consistency Calendar exposes 9 tools: list_templates, get_template_guide, validate_spec, create_calendar, get_status, and 4 more. Their descriptions and schemas cost roughly 772 tokens of context every time the server is loaded.
Does the Consistency Calendar MCP server require authentication?
No. We connected to Consistency Calendar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Consistency Calendar MCP server still maintained?
Consistency Calendar is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.