# Timergy (npm · @timergy/mcp)

Create scheduling polls, vote, and finalize times from AI agents.

- Trust score: 69/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@timergy/mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/dockerdiscordcontrol-timergy/timergy-mcp.md), [page](https://verifymcp.io/servers/dockerdiscordcontrol-timergy/timergy-mcp)

## Channel facts

- Registry: `npm`
- Package: `@timergy/mcp`
- Version: `0.1.4`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/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 51 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 723 tokens (~144/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add dockerdiscordcontrol-timergy -- npx -y @timergy/mcp
```

### Codex

```bash
codex mcp add dockerdiscordcontrol-timergy -- npx -y @timergy/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dockerdiscordcontrol-timergy --command npx --arg -y --arg @timergy/mcp
```

### Hermes

```yaml
mcp_servers:
  dockerdiscordcontrol-timergy:
    command: "npx"
    args: ["-y", "@timergy/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "dockerdiscordcontrol-timergy": {
      "command": "npx",
      "args": [
        "-y",
        "@timergy/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-08-03 (score 69, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 65, +40)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-08-01 (score 25, +5)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass

### 2026-07-31 (score 20, −4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 24, −21)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 45)

First indexed and scored.

## MCP tools (5)

### `create_poll` (~213 tokens)

Create a Timergy scheduling poll (like Doodle) where participants vote on preferred time slots. Provide a title and at least 2-5 time slot options with ISO 8601 date-times (include timezone, e.g. 2026-03-20T18:00:00+02:00 or use UTC with Z suffix). Returns a shareable URL to send to participants and a passphrase for admin access. The passphrase is automatically remembered for finalize_poll. Workflow: create_poll -> share URL -> wait for votes -> get_results -> finalize_poll.

Input parameters:

- `creatorName` (string): Name shown as poll creator (e.g. 'Claude for Max')
- `deadline` (string): Optional voting deadline (ISO 8601)
- `description` (string): Optional poll description
- `location` (string): Optional event location
- `options` (array, required): Time slot options (recommend 3-5)
- `title` (string, required): Poll title (e.g. 'Dinner with Moritz')

### `get_poll` (~75 tokens)

Get poll metadata and time slot options (but NOT votes). Returns title, status, deadline, location, and all available time slots with their option IDs. Use this to retrieve optionId values needed for vote_on_poll or finalize_poll. To see who voted, use get_results instead.

Input parameters:

- `pollId` (string, required): Poll UUID

### `vote_on_poll` (~132 tokens)

Submit votes on a Timergy poll. First call get_poll to retrieve the available optionId values. Each vote maps an optionId to an availability: 'yes' (available), 'maybe' (might work), or 'no' (unavailable). A unique voter token is auto-generated per voter name. Resubmitting with the same voter name updates previous votes.

Input parameters:

- `pollId` (string, required): Poll UUID
- `voterEmail` (string): Optional voter email for finalization notification
- `voterName` (string, required): Name of the voter
- `votes` (array, required): One vote per time slot

### `get_results` (~73 tokens)

Get voting results for a Timergy poll, showing who voted yes/maybe/no for each time slot. Use this after participants have voted to see which slot has the most availability. To finalize, pick the optionId with the most 'yes' votes and call finalize_poll.

Input parameters:

- `pollId` (string, required): Poll UUID

### `finalize_poll` (~117 tokens)

Finalize a poll by picking the winning time slot. Call get_results first to find the best optionId. Uses the passphrase auto-saved from create_poll. If the MCP server was restarted since poll creation, provide the passphrase manually. This locks the poll and notifies participants who provided an email.

Input parameters:

- `optionId` (string, required): Winning time slot option UUID (pick from get_results)
- `passphrase` (string): Admin passphrase (auto-used from create_poll if available)
- `pollId` (string, required): Poll UUID

## Diagnostics

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

## Score history

- 2026-08-03: 69
- 2026-08-02: 65
- 2026-08-01: 25
- 2026-07-31: 20
- 2026-07-30: 24
- 2026-07-28: 24
- 2026-07-27: 45

## Links

- npm package: https://www.npmjs.com/package/@timergy/mcp
- Socket report: https://socket.dev/npm/package/@timergy/mcp
- Repository: https://github.com/timergy-app/timergy
- Changelog RSS feed: https://verifymcp.io/servers/dockerdiscordcontrol-timergy/timergy-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dockerdiscordcontrol-timergy/timergy-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dockerdiscordcontrol-timergy/timergy-mcp