mcpField
U
Uuid Generator X402

Uuid Generator X402

Remote
github.comDeveloper Tools0Updated 8w ago

About Uuid Generator X402

Uuid Generator X402 is an API and MCP server for generating UUID v4, UUID v7, ULID, and nanoid identifiers. It supports batches of up to 100 and uses x402 pay-per-call payments rather than API keys or signup.

Key features

  1. 01Generate UUID v4, UUID v7, ULID, or nanoid
  2. 02Generate up to 100 IDs per request
  3. 03Set nanoid length
  4. 04x402 pay-per-call access

Use cases

  1. 01Creating database record identifiers
  2. 02Generating API keys or session tokens
  3. 03Producing sortable IDs for databases
  4. 04Creating short URL-safe tokens

MCP support

It exposes the utility_generate_uuid tool to MCP clients at a remote MCP endpoint. Calls use x402 micropayments.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://uuid-generator.api.klymax402.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

UUID Generator API

MCP Server x402 License: MIT

Generate UUID v4, v7, ULID, or nanoid identifiers. Batch up to 100 at once. Sortable, compact, or random formats. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "uuid-generator": {
      "url": "https://uuid-generator.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://uuid-generator.api.klymax402.com/api/generate" \
  -H "Content-Type: application/json" \
  -d '{}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
utility_generate_uuidPOST/api/generate$0.003Generate unique identifiers
utility_generate_uuid

Use this when you need to generate unique identifiers for database records, API keys, or session tokens. Returns an array of IDs in the chosen format.

Parameters

NameTypeRequiredDescription
formatstringnoFormat: uuidv4, uuidv7, ulid, nanoid (default: uuidv4)
countnumbernoNumber to generate (default: 1, max: 100)
lengthnumbernoLength for nanoid (default: 21)

Example response:

{"ids":["550e8400-e29b-41d4-a716-446655440000"],"format":"uuidv4","count":1}

When to use: creating primary keys, correlation IDs, or unique file names. Use uuidv7 or ulid WHEN you need time-sortable IDs for databases. Use nanoid FOR short URL-safe tokens.

Not for: hashing (use crypto_generate_hash), password generation (use security_check_password), slug generation (use text_generate_slug).

Example agent prompts

  • "Generate unique identifiers for database records, API keys, or session tokens"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.