Generate, validate, and inspect UUIDs (v4 random, v7 time-sorted) via @mukundakatta/uuid-mcp

Recipe: Generate & Validate UUIDs (v4/v7) via @mukundakatta/uuid-mcp v0.1.1

Install & run: npm install @mukundakatta/uuid-mcp && node node_modules/@mukundakatta/uuid-mcp/dist/server.js (stdio)

Tools (2)

Verified Execution Trace (12 calls, 100% success, p50=11.3ms)

generate({})
  => {"version":"v4","uuids":["7490db6b-098d-4b9f-8f39-cbcd143c2f8c"]} [18ms]

generate({version:"v4"})
  => {"version":"v4","uuids":["3c0c0dc5-9ed9-4f2a-8b9d-cdb2435ba452"]} [40ms]

generate({version:"v7"})
  => {"version":"v7","uuids":["019f046b-db3a-78e9-86e8-038baae1547b"]} [11ms]

generate({version:"v7"})  // second v7 — later timestamp in prefix
  => {"version":"v7","uuids":["019f046b-db3c-79d9-b2a2-d6c135148e09"]} [7ms]

generate({count:5})
  => {"version":"v4","uuids":["fd726157-412b-4d62-...","7de8210e-1151-497b-...","9939aa3b-ce03-4cdc-...","7545e7ec-0013-43ed-...","3f73e772-c185-4a38-..."]} [141ms]

generate({version:"v7",count:3})
  => {"version":"v7","uuids":["019f046b-dc39-7697-...","019f046b-dc39-749a-...","019f046b-dc39-74f1-..."]} [94ms]

validate({uuid:"b8606f7d-d4aa-45e6-85c6-da82a78c37d0"})
  => {"valid":true,"version":4,"variant":"rfc4122"} [11ms]

validate({uuid:"not-a-uuid"})
  => {"valid":false,"error":"not a UUID"} [26ms]

validate({uuid:"00000000-0000-0000-0000-000000000000"})
  => {"valid":true,"variant":"nil"} [8ms]

validate({uuid:"123e4567-e89b-12d3-a456-426614174000"})
  => {"valid":true,"version":1,"variant":"rfc4122"} [8ms]

validate({uuid:"FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF"})
  => {"valid":true,"version":15,"variant":"future"} [3ms]

Key Gotchas

1. `version` param is STRING `"v4"`/`"v7"` — integers like 4 or 7 technically work but bypass the enum and produce v4 UUIDs regardless.
2. No `decode` tool — only generate and validate. Validation returns version+variant but no timestamp extraction from v7.
3. v7 UUIDs have correct version bits — the M nibble is 7 (e.g., 019f046b-db3a-78e9-...), confirming proper RFC 9562 generation.
4. v7 batch UUIDs within same ms are NOT lexicographically sorted — the random component varies, so [...-7697, ...-749a, ...-74f1] is not in order. Sort explicitly if needed.
5. Nil UUID recognized — 00000000-... returns {valid:true, variant:"nil"} without a version.
6. Max UUID recognized — FFFFFFFF-... returns {valid:true, version:15, variant:"future"}.
7. Case-insensitive — uppercase UUIDs validate fine.
8. `count` caps at 1000 — schema enforces minimum:1, maximum:1000.
9. First call ~140ms for batch (JIT + generation), single calls 3-40ms.