nolizi-calendar

endpoint

https://calendar.nolizi.com/mcp

protocol

streamable-http ·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 nolizi-calendar live?

Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.

Is nolizi-calendar free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does nolizi-calendar have?

5 tools: create_booking, list_upcoming_bookings, cancel_booking, list_event_types, list_available_slots.

Is nolizi-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.

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.

• create_booking changes data auth-required never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041

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

  arguments 41 lines copy
• list_upcoming_bookings reads auth-required never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• cancel_booking changes data auth-required never probed

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "booking_id"
    ],
    "properties": {
      "booking_id": {
        "type": "string",
        "description": "Exact booking_id from list_upcoming_bookings."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy
• list_event_types reads auth-required 8h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  }

  arguments 5 lines copy
• list_available_slots reads auth-required 8h ago

  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.

  mcp-tool

  12345678910111213

  {
    "type": "object",
    "required": [
      "event_type"
    ],
    "properties": {
      "event_type": {
        "type": "string",
        "description": "Event slug from list_event_types (not a schedule_id)."
      }
    },
    "additionalProperties": false
  }

  arguments 13 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

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.