Timergy
NPM · @TIMERGY/MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 51 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @timergy/mcp
claude mcp add dockerdiscordcontrol-timergy -- npx -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": {
"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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +40
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- 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. security
- Capabilities: pass → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 45
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@timergy/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.