Nolizi Calendar
REMOTE · CALENDAR.NOLIZI.COM · SCANNED OCT 4
Free scheduling your agent can book through: live availability, booking, verification, cancel.
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 → Why this is hard to score →
Endpoint Security51
- 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 (cancel_booking). 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 707 tokens (~141/item across 5 items; 5 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Nolizi Calendar MCP server?
Nolizi Calendar is a hosted endpoint at https://calendar.nolizi.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 · calendar.nolizi.com
claude mcp add --transport http com-nolizi-calendar-calendar 'https://calendar.nolizi.com/mcp'
{
"mcpServers": {
"com-nolizi-calendar-calendar": {
"url": "https://calendar.nolizi.com/mcp"
}
}
} {
"servers": {
"com-nolizi-calendar-calendar": {
"type": "http",
"url": "https://calendar.nolizi.com/mcp"
}
}
} [mcp_servers.com-nolizi-calendar-calendar] url = "https://calendar.nolizi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-nolizi-calendar-calendar": {
"type": "remote",
"url": "https://calendar.nolizi.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-nolizi-calendar-calendar --url 'https://calendar.nolizi.com/mcp' --transport streamable-http
mcp_servers:
com-nolizi-calendar-calendar:
url: "https://calendar.nolizi.com/mcp" {
"McpServers": {
"com-nolizi-calendar-calendar": {
"Transport": "http",
"Url": "https://calendar.nolizi.com/mcp"
}
}
} assistant mcp add com-nolizi-calendar-calendar -t streamable-http -u 'https://calendar.nolizi.com/mcp'
{
"mcpServers": {
"com-nolizi-calendar-calendar": {
"type": "http",
"url": "https://calendar.nolizi.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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 4 Oct 2026 · Probed https://calendar.nolizi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nolizi.com | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a6bb7506385a49500e17a2d46ac8e108 |
| SANs: nolizi.com, calendar.nolizi.com, *.calendar.nolizi.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 calendar.nolizi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nolizi.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=86400 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://calendar.nolizi.com/mcp | Verified | 200 | |
| http (plaintext) | http://calendar.nolizi.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 →
cancel_booking Cancel a booking ~94
Cancel a confirmed booking. This notifies the attendee and removes the meeting from connected calendars, and it cannot be undone. Use an exact booking_id taken from list_upcoming_bookings — never a guessed or reconstructed one. Cancelling one occurrence of a grouped or recurring booking can affect several meetings, so confirm with the person which meetings they mean.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | Exact booking_id from list_upcoming_bookings. |
No output schema declared.
No examples provided.
create_booking Create a booking ~250
Book a real meeting. This sends invitations and writes to connected calendars, and it cannot be undone except by cancelling. Ask the person to confirm the event, the exact time and the attendee details before calling it, and use their real name and email — never a placeholder. The start and end must be copied verbatim from a recent list_available_slots response; this server re-checks them against live availability and refuses times it cannot find. There is no idempotency key: if this call returns an uncertain outcome, do not call it again — call list_upcoming_bookings and read what actually happened.
| Name | Type | Req | Description |
|---|---|---|---|
| booker_tz | string | – | Attendee IANA timezone, e.g. Europe/Berlin. Defaults to UTC. |
| string | yes | The attendee’s real email address. Invitations go here. | |
| end | string | yes | The matching end from that same slot. |
| event_type | string | yes | Event slug from list_event_types. |
| name | string | yes | The attendee’s real name. |
| note | string | – | Optional note shared with the host (max 2000 characters). |
| start | string | yes | Start, copied exactly from a fresh list_available_slots response. |
No output schema declared.
No examples provided.
list_available_slots List available times ~92
Return the live available start/end pairs for one event type. These are real times on a real calendar: show them to the person and let them choose. Do not invent, extrapolate or round a time that is not in this response. Convert times for display only — pass the original values back to create_booking unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| event_type | string | yes | Event slug from list_event_types (not a schedule_id). |
No output schema declared.
No examples provided.
list_event_types List event types ~69
List the bookable event types owned by the configured Nolizi Calendar account. Start here: the returned slug is what every other tool needs. Never guess a slug. Events with required custom questions or email verification cannot be booked through this API — send the person to the event’s public booking page instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_upcoming_bookings List upcoming bookings ~52
List up to 100 upcoming confirmed bookings. This is the only way to verify that a booking exists. Use it after every create or cancel, and use it first whenever a write returned an uncertain outcome.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Nolizi Calendar MCP server?
Nolizi Calendar is an MCP server listed in the public MCP registry as com.nolizi.calendar/calendar. Free scheduling your agent can book through: live availability, booking, verification, cancel. This page covers its hosted endpoint (https://calendar.nolizi.com/mcp).
Is the Nolizi Calendar MCP server safe to use?
Nolizi Calendar scores 69 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 Nolizi Calendar MCP server expose?
Nolizi Calendar exposes 5 tools: list_event_types, list_available_slots, list_upcoming_bookings, create_booking, cancel_booking. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.
Does the Nolizi Calendar MCP server require authentication?
No. We connected to Nolizi Calendar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nolizi Calendar MCP server still maintained?
Nolizi Calendar is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.