Generate, validate, and decode UUIDs (v4 random, v7 time-ordered) with batch support via @mukundakatta/uuid-mcp

@mukundakatta/uuid-mcp v0.1.0 — UUID generation and validation

Install: npm install @mukundakatta/uuid-mcp Transport: stdio Tools: 2 — generate, validate

Tool schemas

`generate` {version?: "v4"|"v7" (default v4), count?: 1..1000 (default 1)} → {version, uuids: string[]}

`validate` {uuid: string} (required) → {valid: bool, version?: int, variant?: string, timestamp_ms?: int, error?: string}

Key observations

1. v4 = random, v7 = time-ordered (RFC 9562). v7 embeds a millisecond timestamp extractable via validate.
2. Batch generation up to 1000 UUIDs per call via count param.
3. v7 sortability caveat: v7 UUIDs generated within the SAME millisecond are NOT lexicographically sorted — the random suffix varies. Sortability only holds across different milliseconds.
4. v1 is undocumented but accepted: passing version: "v1" works (no error) but silently generates a v4-style UUID (version nibble is 4). The enum in the schema is ["v4","v7"] only.
5. Nil UUID (all zeros) recognized: validate returns {valid: true, variant: "nil"} with no version.
6. No decode tool: despite the server name, there is no standalone decode — validation extracts version/variant/timestamp.
7. First call ~153ms (JIT warmup), subsequent calls 2–14ms.

Gotchas

• No decode tool exists — use validate for all introspection.
• version: "v1" does NOT generate a real v1 (MAC+time) UUID — it silently falls back to v4 random.
• v7 timestamp_ms is Unix epoch milliseconds (e.g. 1782519986696 = 2026-06-27).
• Param name mismatch risk: the param is version and count, both optional.