io.github.biswajitpanday/currentdt-mcp
NPM · @STRIX-AI/CURRENTDT-MCP · SCANNED SEP 29
Current date and time for AI assistants: UTC, local+offset and epoch together. Any IANA zone.
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to biswajitpanday/CurrentDT-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 698 tokens (~349/item across 2 items; 2 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 Management43
- Stability observed for 13 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 io.github.biswajitpanday/currentdt-mcp server?
io.github.biswajitpanday/currentdt-mcp runs locally as an npm package, launched with npx -y @strix-ai/currentdt-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 · @strix-ai/currentdt-mcp
claude mcp add biswajitpanday-currentdt-mcp -- npx -y @strix-ai/currentdt-mcp
{
"mcpServers": {
"biswajitpanday-currentdt-mcp": {
"command": "npx",
"args": [
"-y",
"@strix-ai/currentdt-mcp"
]
}
}
} {
"servers": {
"biswajitpanday-currentdt-mcp": {
"command": "npx",
"args": [
"-y",
"@strix-ai/currentdt-mcp"
]
}
}
} codex mcp add biswajitpanday-currentdt-mcp -- npx -y @strix-ai/currentdt-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"biswajitpanday-currentdt-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@strix-ai/currentdt-mcp"
],
"enabled": true
}
}
} openclaw mcp add biswajitpanday-currentdt-mcp --command npx --arg -y --arg @strix-ai/currentdt-mcp
mcp_servers:
biswajitpanday-currentdt-mcp:
command: "npx"
args: ["-y", "@strix-ai/currentdt-mcp"] {
"McpServers": {
"biswajitpanday-currentdt-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@strix-ai/currentdt-mcp"
]
}
}
} assistant mcp add biswajitpanday-currentdt-mcp -t stdio -c npx -a -y @strix-ai/currentdt-mcp
{
"mcpServers": {
"biswajitpanday-currentdt-mcp": {
"command": "npx",
"args": [
"-y",
"@strix-ai/currentdt-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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 17 Sept 26 +25
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 16 Sept 26 54
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 29 Sept 2026 · Analysed npm/@strix-ai/currentdt-mcp@2.0.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | biswajitpanday/CurrentDT-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/biswajitpanday/CurrentDT-mcp/.github/workflows/main.yml@refs/heads/master |
| Rekor log index | 2863922193 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6d24e6034b88b968642c6ce7911940bd68b40f3d7f75e176da76e3ac5240d96ed37faf283d4f939fb7fa27bb256ac2c6f6e482e383159bd91ae34e478 |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
convert_timezone Convert a time between timezones ~267
Re-state a time in another timezone, DST-correct for the date in question. Use this instead of adding a remembered offset: offsets change with the calendar, and the hour either side of a changeover is where guesses go wrong. Give `time` with an offset for an exact instant, or without one plus `from` for a wall-clock reading in a named zone.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Token pattern for `formatted`, rendered in `to`. Defaults to ISO with offset. |
| from | string | – | Zone the wall-clock `time` was read in. Required when `time` has no offset. IANA name such as "UTC", "Europe/Berlin", "America/New_York" or "Asia/Kolkata". |
| time | string | yes | ISO 8601. With an offset ("2026-03-29T01:30:00+01:00", "...Z") it pins an instant. Without one ("2026-03-29T01:30:00") it is a wall-clock reading and `from` is required. |
| to | string | yes | Zone to convert into. IANA name such as "UTC", "Europe/Berlin", "America/New_York" or "Asia/Kolkata". |
| Name | Type | Req | Description |
|---|---|---|---|
| dstTransition | boolean | yes | True when the instant is within an hour of a DST changeover in `to` -- the case where a guessed offset is most likely wrong. Trust `local` and `offset` over any assumption. |
| epochMs | integer | yes | Milliseconds since the Unix epoch. |
| formatted | string | yes | The requested `format`, rendered. Same value as the text content. |
| from | string | yes | Zone the input was interpreted in: `from`, or "offset in input". |
| iso | string | yes | The instant as ISO 8601 UTC. Use this for machine timestamps. |
| local | string | yes | Host-local clock reading as ISO 8601 with its real offset, e.g. 2026-08-20T14:31:02.625+02:00. |
| offset | string | yes | Host UTC offset, extended form: "+02:00", "-05:30", "+00:00". |
| timezone | string | yes | IANA zone that `local` and `offset` are stated in, e.g. "Europe/Berlin". |
| utc | string | yes | UTC clock reading. Identical to `iso` in this version. |
No examples provided.
get_current_datetime Get current date and time ~350
Get the current date and time. Call this before writing any date, timestamp, year, changelog entry, migration filename or copyright line -- your training data predates today. The text content is the requested `format` only; read `structuredContent` for the same instant stated as UTC (`iso`, `utc`), host-local with offset (`local`, `offset`, `timezone`) and epoch milliseconds, so there is never any doubt which clock a value came from.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | "iso" (default unless configured otherwise) returns UTC, e.g. 2026-08-20T12:31:02.625Z. Anything else is a token pattern rendered in the host's LOCAL time and must contain at least one token; free te… |
| provider | string | – | "local" (default) reads the system clock. "remote" queries a network time service and fails rather than silently substituting the local clock. |
| timezone | string | – | Zone for `local`, `offset`, `timezone` and any token format. IANA name such as "UTC", "Europe/Berlin", "America/New_York" or "Asia/Kolkata". Defaults to the host machine's zone. Does not affect `iso`… |
| Name | Type | Req | Description |
|---|---|---|---|
| epochMs | integer | yes | Milliseconds since the Unix epoch. |
| formatted | string | yes | The requested `format`, rendered. Same value as the text content. |
| iso | string | yes | The instant as ISO 8601 UTC. Use this for machine timestamps. |
| local | string | yes | Host-local clock reading as ISO 8601 with its real offset, e.g. 2026-08-20T14:31:02.625+02:00. |
| offset | string | yes | Host UTC offset, extended form: "+02:00", "-05:30", "+00:00". |
| provider | string | yes | Which provider actually answered. Differs from the request only on fallback. |
| timezone | string | yes | IANA zone that `local` and `offset` are stated in, e.g. "Europe/Berlin". |
| utc | string | yes | UTC clock reading. Identical to `iso` in this version. |
No examples provided.
What is the io.github.biswajitpanday/currentdt-mcp server?
io.github.biswajitpanday/currentdt-mcp is listed in the public MCP registry as io.github.biswajitpanday/currentdt-mcp. Current date and time for AI assistants: UTC, local+offset and epoch together. Any IANA zone. This page covers its npm package (@strix-ai/currentdt-mcp).
Is the io.github.biswajitpanday/currentdt-mcp server safe to use?
io.github.biswajitpanday/currentdt-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.biswajitpanday/currentdt-mcp server expose?
io.github.biswajitpanday/currentdt-mcp exposes 2 tools: get_current_datetime, convert_timezone. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.
Is the io.github.biswajitpanday/currentdt-mcp server still maintained?
io.github.biswajitpanday/currentdt-mcp is still listed as active in the MCP registry. We last reached this channel on 29 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 io.github.biswajitpanday/currentdt-mcp server under?
io.github.biswajitpanday/currentdt-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.