Timergy
NPM · @TIMERGY/MCP · SCANNED SEP 24
Create scheduling polls, vote, and finalize times from AI agents.
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 103 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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
How do I install the Timergy MCP server?
Timergy runs locally as an npm package, launched with npx -y @timergy/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @timergy/mcp
claude mcp add dockerdiscordcontrol-timergy -- npx -y @timergy/mcp
{
"mcpServers": {
"dockerdiscordcontrol-timergy": {
"command": "npx",
"args": [
"-y",
"@timergy/mcp"
]
}
}
} {
"servers": {
"dockerdiscordcontrol-timergy": {
"command": "npx",
"args": [
"-y",
"@timergy/mcp"
]
}
}
} codex mcp add dockerdiscordcontrol-timergy -- npx -y @timergy/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dockerdiscordcontrol-timergy": {
"type": "local",
"command": [
"npx",
"-y",
"@timergy/mcp"
],
"enabled": true
}
}
} openclaw mcp add dockerdiscordcontrol-timergy --command npx --arg -y --arg @timergy/mcp
mcp_servers:
dockerdiscordcontrol-timergy:
command: "npx"
args: ["-y", "@timergy/mcp"] {
"McpServers": {
"dockerdiscordcontrol-timergy": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@timergy/mcp"
]
}
}
} assistant mcp add dockerdiscordcontrol-timergy -t stdio -c npx -a -y @timergy/mcp
{
"mcpServers": {
"dockerdiscordcontrol-timergy": {
"command": "npx",
"args": [
"-y",
"@timergy/mcp"
]
}
}
} 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.
- 24 Sept 26 −3
- Stability: pass → 0.83 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 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.
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 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.
- 17 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 −4
- Stability: pass → 0.77 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
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 24 Sept 2026 · Analysed npm/@timergy/mcp@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_poll ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Time slot options (recommend 3-5) |
| title | string | yes | Poll title (e.g. 'Dinner with Moritz') |
No output schema declared.
No examples provided.
finalize_poll ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| optionId | string | yes | Winning time slot option UUID (pick from get_results) |
| passphrase | string | – | Admin passphrase (auto-used from create_poll if available) |
| pollId | string | yes | Poll UUID |
No output schema declared.
No examples provided.
get_poll ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pollId | string | yes | Poll UUID |
No output schema declared.
No examples provided.
get_results ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pollId | string | yes | Poll UUID |
No output schema declared.
No examples provided.
vote_on_poll ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pollId | string | yes | Poll UUID |
| voterEmail | string | – | Optional voter email for finalization notification |
| voterName | string | yes | Name of the voter |
| votes | array | yes | One vote per time slot |
No output schema declared.
No examples provided.
What is the Timergy MCP server?
Timergy is an MCP server listed in the public MCP registry as io.github.DockerDiscordControl/timergy. Create scheduling polls, vote, and finalize times from AI agents. This page covers its npm package (@timergy/mcp).
Is the Timergy MCP server safe to use?
Timergy scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 Timergy MCP server expose?
Timergy exposes 5 tools: create_poll, get_poll, vote_on_poll, get_results, finalize_poll. Their descriptions and schemas cost roughly 610 tokens of context every time the server is loaded.
Is the Timergy MCP server still maintained?
Timergy is still listed as active in the MCP registry. We last reached this channel on 24 September 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 Timergy MCP server under?
Timergy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.