# Nolizi Calendar (remote · calendar.nolizi.com)

Free scheduling your agent can book through: live availability, booking, verification, cancel.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `calendar.nolizi.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-nolizi-calendar-calendar/calendar.md), [page](https://verifymcp.io/servers/com-nolizi-calendar-calendar/calendar)

## Channel facts

- Endpoint: `https://calendar.nolizi.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.10.5`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_booking).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-nolizi-calendar-calendar 'https://calendar.nolizi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-nolizi-calendar-calendar": {
      "url": "https://calendar.nolizi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-nolizi-calendar-calendar": {
      "type": "http",
      "url": "https://calendar.nolizi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-nolizi-calendar-calendar]
url = "https://calendar.nolizi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-nolizi-calendar-calendar": {
      "type": "remote",
      "url": "https://calendar.nolizi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-nolizi-calendar-calendar --url 'https://calendar.nolizi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nolizi-calendar-calendar:
    url: "https://calendar.nolizi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-nolizi-calendar-calendar": {
      "Transport": "http",
      "Url": "https://calendar.nolizi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-nolizi-calendar-calendar -t streamable-http -u 'https://calendar.nolizi.com/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 69, +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.

### 2026-10-01 (score 68, +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.

### 2026-09-29 (score 67, +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.

### 2026-09-28 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 66, +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.

### 2026-09-25 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 64, +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.

### 2026-09-22 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `list_event_types` (~69 tokens)

List event types

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.

### `list_available_slots` (~92 tokens)

List available times

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.

Input parameters:

- `event_type` (string, required): Event slug from list_event_types (not a schedule_id).

### `list_upcoming_bookings` (~52 tokens)

List upcoming bookings

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.

### `create_booking` (~250 tokens)

Create a booking

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.

Input parameters:

- `booker_tz` (string): Attendee IANA timezone, e.g. Europe/Berlin. Defaults to UTC.
- `email` (string, required): The attendee’s real email address. Invitations go here.
- `end` (string, required): The matching end from that same slot.
- `event_type` (string, required): Event slug from list_event_types.
- `name` (string, required): The attendee’s real name.
- `note` (string): Optional note shared with the host (max 2000 characters).
- `start` (string, required): Start, copied exactly from a fresh list_available_slots response.

### `cancel_booking` (~94 tokens)

Cancel a booking

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.

Input parameters:

- `booking_id` (string, required): Exact booking_id from list_upcoming_bookings.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-nolizi-calendar-calendar/calendar#diagnostics

## Score history

- 2026-10-04: 69
- 2026-10-03: 69
- 2026-10-02: 68
- 2026-10-01: 68
- 2026-09-30: 67
- 2026-09-29: 67
- 2026-09-28: 66
- 2026-09-27: 66
- 2026-09-26: 65
- 2026-09-25: 65
- 2026-09-24: 64
- 2026-09-23: 64
- 2026-09-22: 63
- 2026-09-21: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://calendar.nolizi.com/mcp
- Authorisation metadata: https://calendar.nolizi.com/.well-known/oauth-protected-resource/mcp
- Website: https://calendar.nolizi.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-nolizi-calendar-calendar/calendar.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nolizi-calendar-calendar/calendar.json
- HTML version of this page: https://verifymcp.io/servers/com-nolizi-calendar-calendar/calendar