# dates-le [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/nolindnaidoo/dates-le  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1538  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dates-le

## Description
Extract dates and timestamps from logs, data files and code, with their format and position.

## Tools
Capabilities this server exposes over MCP:

- **extract_dates** — Extract every date and timestamp from a document, with its notation, epoch value where resolvable, and 1-based line and column. Reads any text: JSON, YAML, CSV, XML, log and plaintext, JavaScript, TypeScript, HTML, TOML and Markdown are named formats, and anything else is scanned with the patterns they share. Recognises ISO 8601 in extended, basic, week and ordinal form, RFC formats, day-first and month-first numeric dates, dates with the month written out, and, when `kinds` includes "unix", Unix timestamps from seconds to nanoseconds.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "dates-le": {
    "command": "npx",
    "args": ["-y","dates-le-mcp"]
  }
}
```

## Documentation

## What dates-le MCP server does

The dates-le MCP server exposes the project’s date-extraction engine through MCP. An agent sends document content to `extract_dates`, rather than asking the server to open a path. Results identify each match’s original notation, its timestamp when the value can be resolved, and its one-based line and column.

The shared parser covers common ISO 8601 forms, RFC 2822 values, Unix epochs, UTC strings, calendar dates, numeric dates, and dates with written English month names. It validates calendar values and ignores values that cannot be resolved. Ambiguous numeric dates use month-first interpretation by default, with an option to select day-first behavior.

## How it works

The server communicates over MCP using stdio. It accepts `content` plus optional arguments: `format`, `filename`, `dedupe`, `dateOrder`, and `maxResults`. Results are limited to 500 by default; when more matches exist, the response includes `meta.truncated`.

Format hints add specialized detection rules without excluding the shared rules. Log and plain-text inputs can recognize timestamped log lines, syslog timestamps, and Apache access-log timestamps. JavaScript and TypeScript inputs also inspect date-related calls such as `new Date()`, `Date.parse()`, `moment()`, `dayjs()`, and `DateTime.fromISO()`. HTML adds support for `datetime` attributes, date-bearing meta tags, and JSON-LD publication or modification fields. XML comments are skipped.

## Setup and configuration

Run the published package with:

```bash
npx -y dates-le-mcp
```

An MCP host can register it with a command of `npx` and the arguments `-y` and `dates-le-mcp`. Pinning a package version is supported, or install it globally with `npm install -g dates-le-mcp` and invoke `dates-le-mcp` directly. A basic health check pipes a JSON-RPC `tools/list` request to the process and confirms that `extract_dates` appears.

No environment variables, API key, or server-specific configuration is required. The dates-le MCP server processes the content supplied by the host, does not read files, and does not make its own network requests.

## Tools and capabilities

The server provides one documented tool:

Supported input hints include JSON, YAML, CSV, XML, logs, plain text, JavaScript, TypeScript, HTML, TOML, Markdown, INI, CFG, CONF, and properties files. Other language identifiers still receive the shared date-pattern scan. Recognized epoch lengths include seconds, milliseconds, microseconds, and nanoseconds when they meet the documented plausibility rules.

## Limitations and notes

Written month names are English only. Syslog timestamps have no year, so the current year is assumed. Timezone abbreviations use fixed offsets rather than zone-aware rules; `IST` is interpreted as India’s offset. Ambiguous numeric dates follow `dateOrder`, which defaults to `mdy`, while dotted numeric dates are always day-first. A ten-digit value in a plausible epoch range can still be indistinguishable from a phone number.

The dates-le MCP server is distributed as `dates-le-mcp` on npm and uses stdio rather than an HTTP endpoint. The README also identifies a registry entry for the server and documents use from VS Code agent mode, Claude Code, Cursor, Windsurf, and other MCP hosts.

_Full upstream README: https://allmcps.com/mcp/dates-le/readme_