Skip to content
BEAD

UUID Generator

Generate UUID v4 (random) and v7 (time-ordered) identifiers, one or many at a time.

🔒 Generated with window.crypto in your browser. Nothing is transmitted.

</>Use this tool programmaticallycurl · JavaScript · MCP

Same tool, callable from any HTTP client or from Claude (via MCP). Anonymous: 100 req/day per IP. Sign up for 1,000 req/day.

curl
curl https://api.b-e-a-d.com/tools/uuid-generator/run \
  -H "Content-Type: application/json" \
  -d '{
  "version": "v4",
  "count": 1,
  "uppercase": false
}'
JavaScript (fetch)
const res = await fetch("https://api.b-e-a-d.com/tools/uuid-generator/run", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
  "version": "v4",
  "count": 1,
  "uppercase": false
}),
});
const data = await res.json();
console.log(data.result);
MCP (Claude Desktop / Claude Code)
# In Claude Desktop / Claude Code, add to your MCP config:
{
  "mcpServers": {
    "bead": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.b-e-a-d.com"]
    }
  }
}

# Then ask Claude to call:
mcp__bead__bead_uuid_generator

Full reference: developer docs · OpenAPI spec

v4 vs v7

  • v4— 122 bits of randomness. Use when you want an opaque, unguessable ID and don't care about ordering.
  • v7 — a 48-bit Unix-ms timestamp followed by 74 random bits. Sortable by time, which makes it a much friendlier primary key for databases that index on insertion order (Postgres btrees, SQLite indices) than v4.

Frequently asked

Should I use v4, v7, or something else?

v4 is random — best when you want unguessable IDs (auth tokens, ephemeral keys). v7 is time-ordered — best when IDs go into a database index, because inserts stay sequential. v1 is timestamp + MAC and is mostly legacy.

Are these really unique?

Practically, yes. v4 has 122 bits of entropy — you'd need to generate billions per second for thousands of years before a collision became likely. v7 is even safer because the timestamp prefix segments the space.

Can I get the same UUID twice on purpose?

Yes — that's exactly what UUID v5/v3 are for (deterministic from a namespace + name). BEAD has a dedicated UUID v3/v5 tool for that.

You might also like