# DayPilot

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

- name: org.daypilot/mcp
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 89/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/org.daypilot%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/org.daypilot%2Fmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "daypilot": {
      "type": "http",
      "url": "https://mcp.daypilot.org/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-8d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: builder_catalog (destructiveHint, openWorldHint); validate_project (destructiveHint, openWorldHint); render_theme (destructiveHint, openWorldHint); …
- pass `tools.token_cost`: about 2,224 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 2,224 tokens to load them all
- tool set hash: 5dad22994ca04cb92086b64a41a7d73e
- badge: [![protogrid quality](https://protogrid.dev/badge/org.daypilot/mcp.svg)](https://protogrid.dev/servers/org.daypilot/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.daypilot.org/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (8)

- `builder_catalog`: 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.
- `fetch`: 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.
- `generate_project`: 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.
- `render_theme`: 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.
- `resolve_package`: 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.
- `search`: 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.
- `theme_manifest`: 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.
- `validate_project`: 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.