# io.github.biswajitpanday/currentdt-mcp (npm · @strix-ai/currentdt-mcp)

Current date and time for AI assistants: UTC, local+offset and epoch together. Any IANA zone.

- Trust score: 85/100 (high trust)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- npm · `@strix-ai/currentdt-mcp`: 85/100 (this document), [markdown](https://verifymcp.io/servers/biswajitpanday-currentdt-mcp/strix-ai-currentdt-mcp.md), [page](https://verifymcp.io/servers/biswajitpanday-currentdt-mcp/strix-ai-currentdt-mcp)

## Channel facts

- Registry: `npm`
- Package: `@strix-ai/currentdt-mcp`
- Version: `2.0.3`
- 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-09-29.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to biswajitpanday/CurrentDT-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add biswajitpanday-currentdt-mcp -- npx -y @strix-ai/currentdt-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "biswajitpanday-currentdt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@strix-ai/currentdt-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "biswajitpanday-currentdt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@strix-ai/currentdt-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add biswajitpanday-currentdt-mcp -- npx -y @strix-ai/currentdt-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add biswajitpanday-currentdt-mcp --command npx --arg -y --arg @strix-ai/currentdt-mcp
```

### Hermes

```yaml
mcp_servers:
  biswajitpanday-currentdt-mcp:
    command: "npx"
    args: ["-y", "@strix-ai/currentdt-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "biswajitpanday-currentdt-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@strix-ai/currentdt-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add biswajitpanday-currentdt-mcp -t stdio -c npx -a -y @strix-ai/currentdt-mcp
```

### Other

```json
{
  "mcpServers": {
    "biswajitpanday-currentdt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@strix-ai/currentdt-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-09-28 (score 85, +1)

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

### 2026-09-26 (score 84, +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.

### 2026-09-25 (score 83, 0)

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

### 2026-09-24 (score 83, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-17 (score 79, +25)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-09-16 (score 54)

First indexed and scored.

## MCP tools (2)

### `get_current_datetime` (~350 tokens)

Get current date and time

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.

Input parameters:

- `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`…

Output parameters:

- `epochMs` (integer): Milliseconds since the Unix epoch.
- `formatted` (string): The requested `format`, rendered. Same value as the text content.
- `iso` (string): The instant as ISO 8601 UTC. Use this for machine timestamps.
- `local` (string): Host-local clock reading as ISO 8601 with its real offset, e.g. 2026-08-20T14:31:02.625+02:00.
- `offset` (string): Host UTC offset, extended form: "+02:00", "-05:30", "+00:00".
- `provider` (string): Which provider actually answered. Differs from the request only on fallback.
- `timezone` (string): IANA zone that `local` and `offset` are stated in, e.g. "Europe/Berlin".
- `utc` (string): UTC clock reading. Identical to `iso` in this version.

### `convert_timezone` (~267 tokens)

Convert a time between timezones

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.

Input parameters:

- `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, required): 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, required): Zone to convert into. IANA name such as "UTC", "Europe/Berlin", "America/New_York" or "Asia/Kolkata".

Output parameters:

- `dstTransition` (boolean): 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): Milliseconds since the Unix epoch.
- `formatted` (string): The requested `format`, rendered. Same value as the text content.
- `from` (string): Zone the input was interpreted in: `from`, or "offset in input".
- `iso` (string): The instant as ISO 8601 UTC. Use this for machine timestamps.
- `local` (string): Host-local clock reading as ISO 8601 with its real offset, e.g. 2026-08-20T14:31:02.625+02:00.
- `offset` (string): Host UTC offset, extended form: "+02:00", "-05:30", "+00:00".
- `timezone` (string): IANA zone that `local` and `offset` are stated in, e.g. "Europe/Berlin".
- `utc` (string): UTC clock reading. Identical to `iso` in this version.

## Diagnostics

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

## Score history

- 2026-09-29: 85
- 2026-09-28: 85
- 2026-09-27: 84
- 2026-09-26: 84
- 2026-09-25: 83
- 2026-09-24: 83
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 54

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@strix-ai/currentdt-mcp
- Socket report: https://socket.dev/npm/package/@strix-ai/currentdt-mcp
- Repository: https://github.com/biswajitpanday/CurrentDT-mcp
- Changelog RSS feed: https://verifymcp.io/servers/biswajitpanday-currentdt-mcp/strix-ai-currentdt-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/biswajitpanday-currentdt-mcp/strix-ai-currentdt-mcp.json
- HTML version of this page: https://verifymcp.io/servers/biswajitpanday-currentdt-mcp/strix-ai-currentdt-mcp