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.

Calendly

NPM · @PIPEWORX/MCP-CALENDLY · 2 COMPONENTS

Calendly MCP Pack — wraps the Calendly API v2 for scheduling data.

83 Trust /100

Last scanned (22 hours ago)

Scores higher than 76% of npm servers

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-calendly). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 697 tokens (~139/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 Management20
  • Stability observed for 6 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
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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 +1

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

  • 29 Oct 26 80

    First indexed and scored.

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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-calendly@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-calendly
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-calendly/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606652298
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d645746d241d22b87293ce852e2ae8290579d1628705264f5b94ac666d5dbd39ed237c6b9d1f93612a3404fec45282c8c4471cd6aa31ea483b3e5b782

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~644 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
current_user ~67

Get the current Calendly user for the supplied token. Returns the user URI and organization URI — call this FIRST, since list_scheduled_events and list_event_types require a user or organization URI.

NameTypeReqDescription
_apiKeystringyesCalendly personal access token (sent as Bearer token)

No output schema declared.

No examples provided.

get_event ~80

Get a single scheduled event by its UUID (the last path segment of an event URI). Returns full event details including name, times, status, location, and event membership.

NameTypeReqDescription
_apiKeystringyesCalendly personal access token (sent as Bearer token)
uuidstringyesScheduled event UUID (last segment of the event URI).

No output schema declared.

No examples provided.

list_event_types ~158

List bookable event types (meeting templates). Requires a user URI OR an organization URI (get them from current_user). Returns event type URIs, names, durations, scheduling URLs, and active state.

NameTypeReqDescription
_apiKeystringyesCalendly personal access token (sent as Bearer token)
activeboolean–If true, only return active event types.
countnumber–Number of results per page (default 20, max 100).
organizationstring–Organization URI (from current_user). Provide user OR organization.
page_tokenstring–Token from a previous response for the next page.
userstring–User URI (from current_user). Provide user OR organization.

No output schema declared.

No examples provided.

list_invitees ~129

List the invitees of a scheduled event by event UUID. Returns invitee names, emails, status (active/canceled), timezone, and answers to booking questions.

NameTypeReqDescription
_apiKeystringyesCalendly personal access token (sent as Bearer token)
countnumber–Number of results per page (default 20, max 100).
page_tokenstring–Token from a previous response for the next page.
statusstring–Filter invitees by status.
uuidstringyesScheduled event UUID (last segment of the event URI).

No output schema declared.

No examples provided.

list_scheduled_events ~210

List scheduled meetings (events). Requires a user URI OR an organization URI (get them from current_user). Filter by status, time window, and paginate. Returns event URIs/UUIDs, names, start/end times, status, and locations.

NameTypeReqDescription
_apiKeystringyesCalendly personal access token (sent as Bearer token)
countnumber–Number of results per page (default 20, max 100).
max_start_timestring–ISO 8601 timestamp; only events starting at/before this time.
min_start_timestring–ISO 8601 timestamp; only events starting at/after this time.
organizationstring–Organization URI (from current_user). Provide user OR organization.
page_tokenstring–Token from a previous response for the next page.
statusstring–Filter by event status.
userstring–User URI (from current_user). Provide user OR organization.

No output schema declared.

No examples provided.

Install

How do I install the Calendly MCP server?

Calendly runs locally as an npm package, launched with npx -y @pipeworx/mcp-calendly. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-calendly

# add to Claude Code
claude mcp add pipeworx-io-calendly -- npx -y @pipeworx/mcp-calendly
Common questions

What is the Calendly MCP server?

Calendly is an MCP server listed in the public MCP registry as io.github.pipeworx-io/calendly. Calendly MCP Pack, wraps the Calendly API v2 for scheduling data. This page covers its npm package (@pipeworx/mcp-calendly).

Is the Calendly MCP server safe to use?

Calendly scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Calendly MCP server expose?

Calendly exposes 5 tools: current_user, list_scheduled_events, get_event, list_invitees, list_event_types. Their descriptions and schemas cost roughly 644 tokens of context every time the server is loaded.

Is the Calendly MCP server still maintained?

Calendly is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Calendly MCP server under?

Calendly declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.