Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ciceropaul/cicero-booking

REMOTE · ADMIN.CICEROLEARNING.COM

Find open times and book a free Cicero Learning consultation.

+1 this week 79 Trust /100

Last scanned (9 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 443 tokens (~221/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 +1

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

  • 26 Oct 26 +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.

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

Diagnostics

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 5 Nov 2026 · Probed https://admin.cicerolearning.com/api/public/booking/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=admin.cicerolearning.com CN=YR1,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 RSA 2048 SHA256-RSA 55fc02f657a839ae22067391a61473b67e9
SANs: admin.cicerolearning.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of admin.cicerolearning.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
cicerolearning.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
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://admin.cicerolearning.com/api/public/booking/mcp Verified 200
http (plaintext) http://admin.cicerolearning.com/api/public/booking/mcp HTTPS enforced 308 https://admin.cicerolearning.com/api/public/booking/mcp
MCP tools · 2 exposed · ~348 tokens

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 →

Tool Tokens
book_consult ~202

Book a Cicero consultation. Use a startIso/endIso pair returned by list_consult_availability. Returns a confirmation with a manage URL the guest can use to reschedule or cancel.

NameTypeReqDescription
customerEmailstringyesThe guest's email address.
customerNamestringyesThe guest's full name.
customerPhonestring–Optional E.164 mobile (e.g. +14155550123) for SMS reminders.
customerTimezonestringyesThe guest's IANA timezone, e.g. "America/New_York".
endIsostringyesSlot end (UTC ISO-8601) from availability.
eventTypeSlugstringyesThe event type, e.g. "cicero-consult".
notestringyesWhy the guest is booking / what they'd like to discuss (required).
startIsostringyesSlot start (UTC ISO-8601) from availability.

No output schema declared.

No examples provided.

list_consult_availability ~146

List open time slots for a Cicero consultation event type over a date range. Returns UTC ISO-8601 start/end instants the guest can book.

NameTypeReqDescription
daysnumber–Alternative to "to": number of days after "from" to search (default 30).
eventTypeSlugstringyesThe event type to book, e.g. "cicero-consult".
fromstring–ISO-8601 start of the search window. Defaults to now.
tostring–ISO-8601 end of the search window. Defaults to 30 days after "from". Windows wider than 62 days are clamped.

No output schema declared.

No examples provided.

Install

How do I install the io.github.ciceropaul/cicero-booking MCP server?

io.github.ciceropaul/cicero-booking is a hosted endpoint at https://admin.cicerolearning.com/api/public/booking/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 · admin.cicerolearning.com

# add to Claude Code
claude mcp add --transport http ciceropaul-cicero-booking 'https://admin.cicerolearning.com/api/public/booking/mcp'
Common questions

What is the io.github.ciceropaul/cicero-booking MCP server?

io.github.ciceropaul/cicero-booking is an MCP server listed in the public MCP registry as io.github.ciceropaul/cicero-booking. Find open times and book a free Cicero Learning consultation. This page covers its hosted endpoint (https://admin.cicerolearning.com/api/public/booking/mcp).

Is the io.github.ciceropaul/cicero-booking MCP server safe to use?

io.github.ciceropaul/cicero-booking scores 79 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 io.github.ciceropaul/cicero-booking MCP server expose?

io.github.ciceropaul/cicero-booking exposes 2 tools: list_consult_availability, book_consult. Their descriptions and schemas cost roughly 348 tokens of context every time the server is loaded.

Does the io.github.ciceropaul/cicero-booking MCP server require authentication?

No. We connected to io.github.ciceropaul/cicero-booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.ciceropaul/cicero-booking MCP server still maintained?

io.github.ciceropaul/cicero-booking is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.