consistency-calendar
https://consistencycalendar.com
Registry code: fbfa032e5cb9e406
Turn any goal with a deadline into a private, gamified, evidence-based execution calendar.
from a public catalogue that lists it, not from the operator
- endpoint
- https://consistencycalendar.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is consistency-calendar live?
- Yes — it answered the hub's last check (checked 28m ago). It answered 99% of checks over the last 30 days.
- Is consistency-calendar free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does consistency-calendar have?
- 9 tools: read_document, get_status, revise_calendar, create_share_link, attach_document, create_calendar, get_template_guide, validate_spec, ….
- Is consistency-calendar safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 9 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- turn a goal with a deadline into a training calendar
- check progress and streaks on a goal calendar
- revise a plan after a setback
- create a public progress share link
- takes → gives
- text, data, documents → data
- tools
- 5 reads4 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_templates reads open 14h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesread_document reads unknown 7h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "calendar_id", "admin_token", "doc_id" ], "properties": { "doc_id": { "type": "string" }, "admin_token": { "type": "string" }, "calendar_id": { "type": "string" } } }arguments 20 linesget_status reads unknown 7h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "calendar_id", "admin_token" ], "properties": { "today": { "type": "string", "description": "User-local date YYYY-MM-DD; defaults to server UTC date" }, "admin_token": { "type": "string" }, "calendar_id": { "type": "string" } } }arguments 20 linesrevise_calendar changes data unknown never probed
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "calendar_id", "admin_token", "spec" ], "properties": { "spec": { "type": "object", "description": "The full revised SprintSpec v1", "propertyNames": { "type": "string" }, "additionalProperties": {} }, "reason": { "type": "string", "description": "One line on why, for the version history" }, "admin_token": { "type": "string" }, "calendar_id": { "type": "string" } } }arguments 29 linescreate_share_link changes data unknown never probed
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "calendar_id", "admin_token" ], "properties": { "disable": { "type": "boolean", "description": "true to turn an existing share page off" }, "admin_token": { "type": "string" }, "calendar_id": { "type": "string" } } }arguments 20 linesattach_document changes data unknown never probed
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "calendar_id", "admin_token", "name", "content" ], "properties": { "name": { "type": "string", "description": "Short document name, e.g. \"AQA Biology GCSE spec\"" }, "content": { "type": "string", "description": "The full text content" }, "admin_token": { "type": "string" }, "calendar_id": { "type": "string" } } }arguments 26 linescreate_calendar changes data unknown never probed
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "spec" ], "properties": { "spec": { "type": "object", "description": "A SprintSpec v1 that passed validate_spec", "propertyNames": { "type": "string" }, "additionalProperties": {} } } }arguments 17 linesget_template_guide reads unknown 14h ago
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…).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "template_id" ], "properties": { "goal": { "type": "string", "description": "The user's goal in their words, e.g. \"first marathon in April\" — matches an expert playbook when available" }, "template_id": { "type": "string", "description": "One of the ids from list_templates" } } }arguments 17 linesvalidate_spec reads unknown 14h ago
Validate a draft SprintSpec without creating anything. Returns machine-readable errors (fix and retry) and warnings (evidence-based advice — take them seriously).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "spec" ], "properties": { "spec": { "type": "object", "description": "The SprintSpec v1 JSON object", "propertyNames": { "type": "string" }, "additionalProperties": {} } } }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idfbfa032e5cb9e406.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fbfa032e5cb9e406/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fbfa032e5cb9e406?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.