io.github.rog0x/time
NPM · @ROG0X/MCP-TIME-TOOLS
Timezone, dates, cron, timestamps for AI agents
Available components
Last scanned (6 hours ago)
Scores higher than 80% of npm servers
Category Productivity and Notes
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
- 30 of 92 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 228 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1042 tokens (~57/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 −1
- Stability: pass → 0.90 functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- 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 6 Nov 2026 · Analysed npm/@rog0x/mcp-time-tools@1.0.2
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
business_days ~105
Calculate business days between dates or add business days to a date
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Number of business days to add (required for 'add' mode, can be negative) |
| end_date | string | – | End date (required for 'count' mode) |
| mode | string | yes | 'count' to count business days between two dates, 'add' to add business days to a date |
| start_date | string | yes | Start date (ISO 8601) |
No output schema declared.
No examples provided.
convert_timezone ~89
Convert a date/time from one timezone to another
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | yes | Date/time string (ISO 8601 or common formats, e.g. 2025-06-15T14:30:00) |
| from_timezone | string | yes | Source timezone (e.g. America/New_York) |
| to_timezone | string | yes | Target timezone (e.g. Asia/Tokyo) |
No output schema declared.
No examples provided.
countdown ~50
Calculate time remaining until a target date/time
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Starting date/time (ISO 8601). Defaults to now. |
| target | string | yes | Target date/time (ISO 8601) |
No output schema declared.
No examples provided.
cron_next_runs ~67
Calculate the next N execution times for a cron expression
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of next executions to show (max 50) |
| expression | string | yes | Cron expression (5 fields) |
| from | string | – | Starting datetime (ISO 8601). Defaults to now. |
No output schema declared.
No examples provided.
current_time_multi ~46
Show current time in multiple timezones at once
| Name | Type | Req | Description |
|---|---|---|---|
| timezones | array | yes | List of timezone identifiers (e.g. ['America/New_York', 'Asia/Tokyo']) |
No output schema declared.
No examples provided.
current_timestamp ~33
Get the current Unix timestamp and formatted date/time
| Name | Type | Req | Description |
|---|---|---|---|
| timezone | string | – | Timezone for display (default: UTC) |
No output schema declared.
No examples provided.
date_add_subtract ~77
Add or subtract days, weeks, months, or years from a date
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to add (positive) or subtract (negative) |
| date | string | yes | Starting date (ISO 8601, e.g. 2025-06-15) |
| unit | string | yes | Unit of time |
No output schema declared.
No examples provided.
date_difference ~70
Calculate the difference between two dates in various units
| Name | Type | Req | Description |
|---|---|---|---|
| date_a | string | yes | First date (ISO 8601, e.g. 2025-01-01) |
| date_b | string | yes | Second date (ISO 8601, e.g. 2025-12-31) |
No output schema declared.
No examples provided.
date_to_timestamp ~36
Convert a date/time string to Unix timestamps
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | yes | Date/time string (ISO 8601 or common formats) |
No output schema declared.
No examples provided.
format_duration ~68
Convert seconds to human-readable duration (e.g. 2h 30m 15s)
| Name | Type | Req | Description |
|---|---|---|---|
| seconds | number | yes | Duration in seconds |
| style | string | – | Output style: 'short' (2h 30m) or 'long' (2 hours 30 minutes) |
No output schema declared.
No examples provided.
generate_cron ~55
Generate a cron expression from a human-readable description
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Human-readable schedule description (e.g. 'every weekday at 9am', 'every 5 minutes', 'first day of month at midnight') |
No output schema declared.
No examples provided.
list_timezones ~37
List common timezones with their current UTC offsets
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Optional filter string to match timezone names (case-insensitive) |
No output schema declared.
No examples provided.
parse_cron ~41
Parse a cron expression into a human-readable description
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | Cron expression (5 fields: minute hour day-of-month month day-of-week) |
No output schema declared.
No examples provided.
parse_duration ~68
Parse a human-readable duration string to seconds (e.g. '2h 30m', '1 day 3 hours')
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | yes | Human-readable duration (e.g. '2h 30m 15s', '1 day 3 hours', '90 minutes') |
No output schema declared.
No examples provided.
time_ago ~62
Calculate relative time description (e.g. '5 minutes ago', 'in 3 hours')
| Name | Type | Req | Description |
|---|---|---|---|
| datetime | string | yes | Target date/time (ISO 8601) |
| reference | string | – | Reference date/time (ISO 8601). Defaults to now. |
No output schema declared.
No examples provided.
time_difference ~53
Calculate the time difference between two timezones
| Name | Type | Req | Description |
|---|---|---|---|
| timezone_a | string | yes | First timezone (e.g. America/New_York) |
| timezone_b | string | yes | Second timezone (e.g. Asia/Tokyo) |
No output schema declared.
No examples provided.
timestamp_to_date ~56
Convert a Unix timestamp (seconds or milliseconds) to human-readable date formats
| Name | Type | Req | Description |
|---|---|---|---|
| timestamp | number | yes | Unix timestamp (auto-detects seconds vs milliseconds) |
| timezone | string | – | Target timezone for display (default: UTC) |
No output schema declared.
No examples provided.
validate_cron ~29
Validate a cron expression and explain any errors
| Name | Type | Req | Description |
|---|---|---|---|
| expression | string | yes | Cron expression to validate |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/time MCP server?
io.github.rog0x/time runs locally as an npm package, launched with npx -y @rog0x/mcp-time-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-time-tools
claude mcp add rog0x-time -- npx -y @rog0x/mcp-time-tools
What is the io.github.rog0x/time MCP server?
io.github.rog0x/time is an MCP server listed in the public MCP registry as io.github.rog0x/time. Timezone, dates, cron, timestamps for AI agents. This page covers its npm package (@rog0x/mcp-time-tools).
Is the io.github.rog0x/time MCP server safe to use?
io.github.rog0x/time scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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.rog0x/time MCP server expose?
io.github.rog0x/time exposes 18 tools: convert_timezone, list_timezones, current_time_multi, time_difference, date_add_subtract, and 13 more. Their descriptions and schemas cost roughly 1,042 tokens of context every time the server is loaded.
Is the io.github.rog0x/time MCP server still maintained?
io.github.rog0x/time is still listed as active in the MCP registry. We last reached this channel on 6 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.rog0x/time MCP server under?
io.github.rog0x/time 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.rog0x/time MCP server?
VerifyMCP ran 15 checks on io.github.rog0x/time, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.rog0x/time: Security disclosure. 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.