Consistency Calendar
REMOTE · CONSISTENCYCALENDAR.COM · SCANNED AUG 20
Turn any goal with a deadline into a private, gamified, evidence-based execution calendar.
Available components
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 →
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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · consistencycalendar.com
claude mcp add --transport http olliejgooding-consistency-calendar https://consistencycalendar.com/mcp
[mcp_servers.olliejgooding-consistency-calendar] url = "https://consistencycalendar.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"olliejgooding-consistency-calendar": {
"type": "remote",
"url": "https://consistencycalendar.com/mcp",
"enabled": true
}
}
} openclaw mcp add olliejgooding-consistency-calendar --url https://consistencycalendar.com/mcp --transport streamable-http
mcp_servers:
olliejgooding-consistency-calendar:
url: "https://consistencycalendar.com/mcp" {
"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.
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.
- 19 Aug 26 +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.
- 17 Aug 26 +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.
- 15 Aug 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.
- 13 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Aug 26 57
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 20 Aug 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 | 2 Aug 2026 | 31 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 93c619c17297693c0e6b144d1ac3c43b |
| SANs: consistencycalendar.com, www.consistencycalendar.com, *.www.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 |
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 |
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.
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.