- What it does
- Check a UUID against RFC 9562: form, standard lowercase form, variant, version 1 to 8, nil and max, and the time inside v1, v6 and v7 IDs, with a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
uuid_checkat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
UUID Check (Version, Variant, Timestamp) is for coding agents and developers who debug IDs in databases, logs and APIs and need to know what kind of UUID they hold and, for time-based ones, when it was made, worked the same way every time. Check a UUID (GUID) against RFC 9562: whether it is a well-formed UUID, the text form it was sent in (hyphens, braces, urn:uuid:, upper case), its standard lowercase form, the variant, the version (1 to 8) and what that version means, and for the time-based versions the time inside it: v1 and v6 to 100 nanoseconds (UTC, counted from 15 Oct 1582), v7 to the millisecond (Unix time). Also the nil and max UUIDs, the clock sequence and whether the v1 or v6 node looks like a hardware MAC address or a random value. Useful to see when a v1, v6 or v7 ID was made, or why a system refuses an ID. It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Postgres, Gitlab). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Coding agents and developers who debug IDs in databases, logs and APIs and need to know what kind of UUID they hold and, for time-based ones, when it was made, worked the same way every time.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not check that a UUID is unique, registered or in use anywhere, and does not show the node value itself (a v1 node can be a device's hardware address). Does not check how a v4 or v7 was randomised, does not recover the name inside a v3 or v5 (MD5 and SHA-1 are one-way), and shows no time for v2 (DCE Security replaces the low time bits with a local ID) or v8 (the layout is the vendor's). The time in a UUID is whatever the generating system's clock said; it proves nothing about when the record was really made. Times after 9999-12-31 are given as numbers only.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "uuid_check", "arguments": {"uuid": "017F22E2-79B0-7CC3-98C4-DC0C0C07398F"}}}For agents
Tool uuid_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:tccw7oudnlokqsfoz6xm7himke): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): aDey1s4DtpWib3BrRbmBjoUGJz2oMad1/KbUP0Y4gbE=
For agents that search MCP registries for UUID, GUID, RFC 9562 tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to LLPRO: A UUID check is one step of fixing an integration or a data import. Tell LLPRO the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card