IDs-LE MCP server

IDs-LE: The ID That Only Looks Like One Find every identifier in a document, decode the time inside it, and refuse the ones that cannot be named UUID · ULID · NanoID · MongoDB ObjectId · Snowflake

Useful? A star or rating is how other developers find it —

★ GitHub ·

★ Open VSX ·

★ Marketplace

What it does

A support ticket quotes 6a7bb780a1b2c3d4e5f60718 and asks when the record was made. A regex says ObjectId, minted 2026-08-12. It is the front of a git commit hash, and the date is noise that happens to land in a plausible year.

Open a document, run IDs-LE: Extract IDs, and every identifier in it is listed by kind with its line and column, the document's own key path for it, whether it is valid, and — for the six schemes that carry a clock — the instant it was minted, as ISO-8601 UTC. The report opens beside the editor. IDs-LE: Scan Workspace for IDs does the same for every file in a project, and IDs-LE: Scan Folder for IDs for one folder. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).

• Reading a log or a dump — which of these are UUID v7s, and when was each minted?
• Reviewing a config — the placeholder nil UUID that escaped into production
• Before trusting a hex string — whether the document actually says it is an identifier
• Across a project — every file that holds an identifier, and how many, in one table

A run it cannot name honestly is reported with the reason, never dropped. It rewrites nothing.

Install

It refuses rather than guesses

A tool that answers confidently and wrongly is worse than one that stops and names what it needs. So every run this crate will not name is a row in the report with a reason — never a dropped row, never a silent guess.

Shortened. The full README is on GitHub.