# io.github.pglejzer/timepicker-ui-mcp (npm · timepicker-ui-mcp)

MCP server for timepicker-ui: options, events, themes, public API, snippets and time validation.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `timepicker-ui-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pglejzer-timepicker-ui-mcp/timepicker-ui-mcp.md), [page](https://verifymcp.io/servers/pglejzer-timepicker-ui-mcp/timepicker-ui-mcp)

## Channel facts

- Registry: `npm`
- Package: `timepicker-ui-mcp`
- Version: `2.1.0`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1715 tokens (~81/item across 21 items; 17 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.pglejzer/timepicker-ui-mcp server?

io.github.pglejzer/timepicker-ui-mcp runs locally as an npm package, launched with npx -y timepicker-ui-mcp. 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 pglejzer-timepicker-ui-mcp -- npx -y timepicker-ui-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "pglejzer-timepicker-ui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "timepicker-ui-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pglejzer-timepicker-ui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "timepicker-ui-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pglejzer-timepicker-ui-mcp -- npx -y timepicker-ui-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pglejzer-timepicker-ui-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "timepicker-ui-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pglejzer-timepicker-ui-mcp --command npx --arg -y --arg timepicker-ui-mcp
```

### Hermes

```yaml
mcp_servers:
  pglejzer-timepicker-ui-mcp:
    command: "npx"
    args: ["-y", "timepicker-ui-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "pglejzer-timepicker-ui-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "timepicker-ui-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pglejzer-timepicker-ui-mcp -t stdio -c npx -a -y timepicker-ui-mcp
```

### Other

```json
{
  "mcpServers": {
    "pglejzer-timepicker-ui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "timepicker-ui-mcp"
      ]
    }
  }
}
```

## 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-11-05 (score 82, +1)

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

### 2026-11-03 (score 81, +1)

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

### 2026-11-01 (score 80, +1)

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

### 2026-10-30 (score 79, +1)

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

### 2026-10-27 (score 78, +1)

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

### 2026-10-25 (score 77, +1)

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

### 2026-10-23 (score 76, +1)

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

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

## MCP tools (17)

### `list_themes` (~42 tokens)

List timepicker-ui themes

Lists the 12 built-in themes with their CSS import paths. Select one with ui.theme. For a custom look use ui.cssClass (see generate_custom_theme).

### `list_modes` (~26 tokens)

List timepicker-ui UI modes

Lists the UI modes (clock, wheel, compact-wheel) and which plugin each needs.

### `list_plugins` (~30 tokens)

List timepicker-ui plugins

Lists the optional plugins (range, timezone, wheel) with import paths and the option that turns each on.

### `list_events` (~103 tokens)

List timepicker-ui events

Lists the events picker.on(event, handler) can subscribe to, with the payload type and its fields, extracted from source. Internal and deprecated events are left out unless asked for.

Input parameters:

- `includeDeprecated` (boolean): Also list deprecated events such as hide, select:am and select:pm.
- `includeInternal` (boolean): Also list internal events (open:request, range:minute:commit, animation:*). 5.0 removes them from the event map.

### `list_api` (~32 tokens)

List the public API

Lists the TimepickerUI instance and static methods with signatures, deprecations, and the getValue/setValue contract.

### `list_css_classes` (~44 tokens)

List tp-ui- CSS classes

Lists the tp-ui- class names and state modifiers, with an example selector for each styled class. Prefer --tp- variables; class names change in 5.0.

### `list_css_variables` (~90 tokens)

List --tp- CSS variables

Lists the --tp- CSS custom properties with group, default value and whether built-in themes override them. Variables no rule reads are left out unless asked for.

Input parameters:

- `group` (string): Limit to one group, e.g. Color, Typography, Focus, Wheel.
- `includeUnread` (boolean): Also list variables that no rule reads. Setting them changes nothing and 5.0 removes them.

### `get_options` (~108 tokens)

Get grouped options

Returns the grouped options reference (clock, ui, labels, behavior, callbacks, timezone, range, wheel, clearBehavior) with type, default, description and nested fields, extracted from options.d.ts. Deprecated options are left out unless asked for. Pass a group to narrow it.

Input parameters:

- `group` (string): Limit to a single option group.
- `includeDeprecated` (boolean): Also return deprecated options (old names that still work in 4.x and are removed in 5.0).

### `explain_option` (~83 tokens)

Explain a single option

Returns the full detail (type, default, description, example, deprecation, nested fields) for one option. Use a dotted name for nested fields, e.g. "disabledTime.ranges".

Input parameters:

- `group` (string, required): Option group.
- `name` (string, required): Option name within the group, e.g. "showSeconds" or "disabledTime.ranges".

### `get_theme` (~43 tokens)

Get a built-in theme variable set

Returns the --tp- CSS variables a built-in theme sets, with their values, to start a custom theme from.

Input parameters:

- `name` (string, required): Built-in theme name.

### `framework_recipe` (~52 tokens)

Framework integration recipe

Returns an integration recipe (lifecycle, SSR notes and code) for vanilla, react, react-wrapper (timepicker-ui-react), next, vue, angular or svelte.

Input parameters:

- `framework` (string, required): Target framework.

### `migration_guide` (~104 tokens)

Migration guide

Returns migration guidance. "v3->v4": flat to grouped option mapping. "v4.3->v4.4" and "v4.4->v4.5": non-breaking changes, with every renamed option. "v4.5->v5": draft list of what 5.0 removes and changes, and the steps that work on 4.5.0 today.

Input parameters:

- `path` (string): Which migration to return.

### `generate_snippet` (~163 tokens)

Generate a timepicker-ui setup snippet

Generates a ready-to-paste vanilla JS or React snippet wiring up TimepickerUI with the chosen theme, mode, clock type, seconds and plugins (CSS imports and plugin registration included). For full framework lifecycle and SSR notes, use framework_recipe.

Input parameters:

- `clockType` (string): 12-hour, 24-hour, or 'auto' (from the browser locale).
- `framework` (string): Output flavor.
- `mode` (string): UI mode.
- `plugins` (array): Plugins to import and register. wheel is added for the wheel modes.
- `selector` (string): CSS selector of the target input (vanilla only).
- `showSeconds` (boolean): Add a seconds field (clock.showSeconds).
- `theme` (string): Theme name.

### `generate_custom_theme` (~151 tokens)

Generate a custom theme stylesheet

Writes the CSS for a custom theme applied with ui.cssClass: a .tp-ui-wrapper.<name> block of --tp- variables. Pass `overrides` to emit only those, or leave it empty for an editable scaffold of the variables built-in themes change. Unknown variables and variables no rule reads are reported.

Input parameters:

- `name` (string, required): Class name for ui.cssClass, e.g. 'ocean'. Letters, digits, - and _.
- `onlyCommon` (boolean): For the scaffold, include only the variables built-in themes override.
- `overrides` (object): Map of CSS variables to values, e.g. { 'tp-primary': '#0ea5e9' }.

### `validate_time` (~104 tokens)

Validate a time string

Validates a time string against a 12h or 24h clock and returns the parsed parts. Accepts "HH:MM", "HH:MM:SS", "h:MM AM/PM" and "h:MM:SS AM/PM".

Input parameters:

- `clockType` (string)
- `time` (string, required): The time string, e.g. "14:30", "14:30:15" or "2:30:15 PM".

### `validate_disabled_time` (~141 tokens)

Validate a disabledTime config

Validates a clock.disabledTime config: hours, minutes and seconds lists, and range strings in ranges ("10:00 AM - 12:00 PM", "10:00:30 - 10:05"). Returns per-issue feedback.

Input parameters:

- `clockType` (string)
- `hours` (array): Disabled hours.
- `interval`: Deprecated old name of ranges; ranges wins when both are set.
- `minutes` (array): Disabled minutes.
- `ranges`: Range string or array, e.g. "10:00 AM - 12:00 PM".
- `seconds` (array): Disabled seconds (used with clock.showSeconds).

### `search_reference` (~109 tokens)

Search the timepicker-ui reference

Keyword search across options (including nested fields), events, CSS variables, CSS classes, methods, themes and troubleshooting entries. Use it when you do not know the exact name. Pass a few keywords, not a sentence, e.g. "disable time range", "focus ring color" or "seconds increment". Deprecated items rank lower and are flagged.

Input parameters:

- `limit` (integer): Maximum number of results.
- `query` (string, required): Keywords, e.g. "seconds increment" or "backdrop".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pglejzer-timepicker-ui-mcp/timepicker-ui-mcp#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72

## Common questions

### What is the io.github.pglejzer/timepicker-ui-mcp server?

io.github.pglejzer/timepicker-ui-mcp is listed in the public MCP registry as io.github.pglejzer/timepicker-ui-mcp. MCP server for timepicker-ui: options, events, themes, public API, snippets and time validation. This page covers its npm package (timepicker-ui-mcp).

### Is the io.github.pglejzer/timepicker-ui-mcp server safe to use?

io.github.pglejzer/timepicker-ui-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.pglejzer/timepicker-ui-mcp server expose?

io.github.pglejzer/timepicker-ui-mcp exposes 17 tools: list_themes, list_modes, list_plugins, list_events, list_api, and 12 more. Their descriptions and schemas cost roughly 1,425 tokens of context every time the server is loaded.

### Is the io.github.pglejzer/timepicker-ui-mcp server still maintained?

io.github.pglejzer/timepicker-ui-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.pglejzer/timepicker-ui-mcp server under?

io.github.pglejzer/timepicker-ui-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.pglejzer/timepicker-ui-mcp server?

VerifyMCP ran 16 checks on io.github.pglejzer/timepicker-ui-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/timepicker-ui-mcp
- Socket report: https://socket.dev/npm/package/timepicker-ui-mcp
- Repository: https://github.com/pglejzer/timepicker-ui
- Changelog RSS feed: https://verifymcp.io/servers/pglejzer-timepicker-ui-mcp/timepicker-ui-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/pglejzer-timepicker-ui-mcp/timepicker-ui-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pglejzer-timepicker-ui-mcp/timepicker-ui-mcp.json
- HTML version of this page: https://verifymcp.io/servers/pglejzer-timepicker-ui-mcp/timepicker-ui-mcp