Random UUID v4 (RFC 9562) as an HTTP API: 1-100 UUIDs per call, in uuid, URN, hex or integer...
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose (returning a UUID) is unambiguous despite the noisy description about x402 pricing.
get_uuid follows a clear snake_case verb_noun convention, but with a single tool there is no pattern to actually verify consistency against.
A single tool is very thin for a server whose domain (UUID generation) typically implies bulk generation, version/template selection, and validation. It only earns a point above the minimum because a minimal generator can technically be a one-operation service.
Only generation is exposed: no bulk generation, no UUID version control (v1/v4/v7), no parsing/validation of existing UUIDs, and no configuration options. Agents needing anything beyond one random UUID hit a dead end.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Generate UUID v4/v5/v7, ULID and NanoID values and inspect UUIDs (version, variant, timestamp).
Pay-per-call dev utilities (hash, base64, uuid, URL, time, NIP-19, BOLT11) via x402 USDC on Base.
Add one secure layer between your agents and this server.