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.

DayPilot

REMOTE · MCP.DAYPILOT.ORG

Official DayPilot references, release packages, CSS themes and verified starter projects.

Available components

0 this week 83 Trust /100

Last scanned (21 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1246 tokens (~155/item across 8 items; 8 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 Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 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.

  • 8 Nov 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.

  • 6 Nov 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
  • 5 Nov 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.

  • 3 Nov 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.

  • 1 Nov 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.

  • 30 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.

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 21 Nov 2026 · Probed https://mcp.daypilot.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.daypilot.org CN=YE2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA384 552d8406260d0d3c51688d47307a2f7c414
SANs: mcp.daypilot.org
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.daypilot.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
daypilot.org. No DS 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
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.daypilot.org/mcp Verified 200
http (plaintext) http://mcp.daypilot.org/mcp HTTPS enforced 308 https://mcp.daypilot.org/mcp
MCP tools · 8 exposed · ~1,054 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
builder_catalog ~123

Discover Builder components, targets, settings, option IDs and defaults for deliberately creating a new project. Omit all filters for components; supply component for targets/settings; add edition and target for explicit option support. Target requires edition. Use catalogRevision in validate_project. Builder covers a configurable subset; absent settings do not establish unsupported product features.

NameTypeReqDescription
componentstring–Optional Builder component; omit for the component inventory
editionstring–Optional lite or pro; requires component
targetstring–Optional advertised concrete target or alias; requires component and edition
NameTypeReqDescription
apiVersionstringyes–
catalogRevisionstringyes–
componentstring––
componentsnull|array––
editionstring––
notestringyes–
scopestringyes–
settingsnull|arrayyes–
settingsFormatstring––
sourceUrlstringyes–
targetnull|object––
targetsnull|arrayyes–

No examples provided.

fetch ~151

Read the published DayPilot API/documentation/CODE article or JavaScript demo Markdown at a canonical source URL. Preserves examples and edition qualifications. Results include source, revision, content and continuation; pass nextOffset with the same revision to continue. References describe the current documentation, not every installed version.

NameTypeReqDescription
maxCharsinteger–Maximum content characters, default 24000, maximum 48000
offsetinteger–Unicode character offset, default zero
revisionstring–Revision from the previous response to ensure consistent continuation
urlstringyesCanonical published article URL on doc.daypilot.org, api.daypilot.org, code.daypilot.org, or javascript.daypilot.org/demo/
NameTypeReqDescription
availabilitynull|array––
canonicalUrlstringyes–
contentobjectyes–
lastModifiedstring––
nextOffsetnull|integer––
offsetintegeryes–
revisionstringyes–
titlestringyes–
totalCharsintegeryes–
truncatedbooleanyes–
versionScopestringyes–

No examples provided.

generate_project ~151

Generate and verify a new Builder project ZIP using the same validated specification plus expectedProjectDigest. Returns a verified receipt and exact canonical POST download request, not ZIP bytes or a saved file. Download using that request, verify archive SHA-256 before extracting into a new directory, then follow generated README/AGENTS and check installation/build/runtime. Pro projects contain an evaluation trial. Never overwrite an existing app.

NameTypeReqDescription
catalogRevisionstringyes–
componentstringyes–
editionstringyes–
expectedProjectDigeststringyesprojectDigest returned by validate_project for the same specification
projectNamestringyes–
settingsobjectyes–
targetstringyes–
NameTypeReqDescription
archiveobjectyes–
downloadobjectyes–
generatedbooleanyes–
guidancenull|arrayyes–
validationobjectyes–

No examples provided.

render_theme ~173

Render complete CSS from a current theme_manifest revision, a unique CSS prefix and optional property overrides. Uses canonical defaults and validates settings. Returns CSS, SHA-256 and application guidance without saving a theme. Load CSS globally and use the prefix in the component's theme property; verify installed typings.

NameTypeReqDescription
componentstringyesComponent from theme_manifest: scheduler, calendar, month, gantt, kanban, or navigator
prefixstringyesCSS prefix: 1–64 lower-case letters, digits or underscores, starting with a letter or underscore
propertiesobject–Optional property overrides; booleans for checkbox, integers or canonical integer strings for number, strings for text/color/select. Omitted properties inherit source defaults
revisionstringyesRequired revision returned by theme_manifest for this component
NameTypeReqDescription
componentstringyes–
cssstringyes–
cssSha256stringyes–
designerUrlstringyes–
generatorVersionstringyes–
manifestUrlstringyes–
prefixstringyes–
revisionstringyes–
schemaVersionstringyes–
usagestringyes–

No examples provided.

resolve_package ~108

Resolve the latest official DayPilot Lite or Pro release for JavaScript, React, Angular or Vue. Returns package identity, license and installation guidance; Pro installation is a trial. Preserve an existing application's installed version and licensed dependency unless an upgrade is requested. Does not install packages or verify historical compatibility.

NameTypeReqDescription
editionstringyesRequired edition: lite or pro; preserve the edition already used by an existing application
frameworkstringyesRequired framework: javascript, react, angular, or vue
NameTypeReqDescription
documentationUrlstringyes–
editionstringyes–
frameworkstringyes–
guidancenull|arrayyes–
installCommandstringyes–
installUrlstring––
installationKindstringyes–
latestReleaseVersionstringyes–
licensestringyes–
packageNamestringyes–
sourceUrlstringyes–
versionSchemestringyes–

No examples provided.

search ~117

Search official DayPilot documentation, API references, examples and release information. Accepts task descriptions or exact API identifiers. Returns ranked sources and exact-match groups with canonical URLs; use fetch to inspect supported results before making implementation claims.

NameTypeReqDescription
limitinteger–Maximum returned results, default 8, maximum 20
querystringyesTask or exact API identifier to search in official DayPilot sources
scopestring–Optional existing Search scope: api, documentation, demos, tutorials, release-notes, forum, or sites
NameTypeReqDescription
generationstring––
groupsnull|array––
notestring––
querystringyes–
resultsnull|arrayyes–
searchUrlstringyes–
truncatedbooleanyes–

No examples provided.

theme_manifest ~61

Discover supported theme settings, defaults and value domains for a DayPilot component. Returns a revision required by render_theme. Inspect the manifest before choosing overrides.

NameTypeReqDescription
componentstringyesComponent: scheduler, calendar, month, gantt, kanban, or navigator
NameTypeReqDescription
apiVersionstringyes–
componentstringyes–
designerUrlstringyes–
generatorVersionstringyes–
manifestUrlstringyes–
notestringyes–
propertyCountintegeryes–
revisionstringyes–
schemaVersionstringyes–
sectionsnull|arrayyes–
titlestringyes–

No examples provided.

validate_project ~170

Preflight a new Builder project using a discovered catalogRevision, component, edition, target, projectName and setting-ID to option-ID map ({} uses defaults). Returns effective settings, qualified release identity, warnings and projectDigest for generate_project. Validates generation only; does not install, build or run the application. Preserve an existing application instead of regenerating it.

NameTypeReqDescription
catalogRevisionstringyesCurrent catalogRevision from builder_catalog
componentstringyes–
editionstringyes–
projectNamestringyesNew project slug: lowercase letters, digits and single hyphens; maximum 60 characters
settingsobjectyesRequired canonical setting-ID to option-ID map; empty object uses catalog defaults
targetstringyesAdvertised concrete target ID or alias
NameTypeReqDescription
apiVersionstringyes–
catalogRevisionstringyes–
componentstringyes–
editionstringyes–
effectiveSettingsobjectyes–
fileCountintegeryesNumber of regular files; ZIP directory entries are excluded
guidancenull|arrayyes–
projectDigeststringyes–
projectNamestringyes–
releaseobjectyes–
scopestringyes–
settingsFormatstringyes–
targetobjectyes–
uncompressedBytesintegeryesSum of uncompressed regular file bytes; directories contribute zero
validbooleanyes–
warningsnull|arrayyes–

No examples provided.

Install

How do I install the DayPilot MCP server?

DayPilot is a hosted endpoint at https://mcp.daypilot.org/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 · mcp.daypilot.org

# add to Claude Code
claude mcp add --transport http org-daypilot-mcp 'https://mcp.daypilot.org/mcp'
Common questions

What is the DayPilot MCP server?

DayPilot is an MCP server listed in the public MCP registry as org.daypilot/mcp. Official DayPilot references, release packages, CSS themes and verified starter projects. This page covers its hosted endpoint (https://mcp.daypilot.org/mcp).

Is the DayPilot MCP server safe to use?

DayPilot scores 83 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 DayPilot MCP server expose?

DayPilot exposes 8 tools: builder_catalog, fetch, generate_project, render_theme, resolve_package, and 3 more. Their descriptions and schemas cost roughly 1,054 tokens of context every time the server is loaded.

Does the DayPilot MCP server require authentication?

No. We connected to DayPilot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DayPilot MCP server still maintained?

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

What did VerifyMCP test on the DayPilot MCP server?

VerifyMCP ran 13 checks on DayPilot, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.