UUID MCP Provider
Proveedor de UUID MCP
Un servidor de Protocolo de Contexto de Modelo (MCP) simple que proporciona UUID basados en marcas de tiempo cada vez que lo llama un LLM.
Características
Proporciona una única herramienta:
generateUuidUtiliza UUID v7 para identificadores únicos basados en marcas de tiempo
Interfaz sencilla que no requiere parámetros de entrada
Fácil integración con Claude y otros LLM
Related MCP server: MCP UUID Server
Instalación
# Install dependencies
npm install
# Build the project
npm run buildUso
Puedes ejecutar el servidor directamente:
npm startIntegración con Claude Desktop
Para integrarlo con Claude Desktop, agregue lo siguiente a su archivo de configuración de Claude Desktop:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonVentanas:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"uuid-provider": {
"command": "node",
"args": ["/absolute/path/to/uuid-mcp/build/index.js"]
}
}
}Reemplace /absolute/path/to/uuid-mcp/build/index.js con la ruta absoluta a su archivo index.js compilado.
Después de actualizar la configuración, reinicie Claude Desktop para ver la herramienta de generación de UUID disponible.
Cómo funciona
Este servidor utiliza el paquete oficial uuid para generar identificadores UUID v7. El UUID v7 está diseñado específicamente para basarse en marcas de tiempo, manteniendo sólidas garantías de unicidad.
Incorpora una marca de tiempo Unix con precisión de milisegundos.
Agrega datos aleatorios para garantizar la singularidad incluso cuando se generan múltiples identificaciones en el mismo milisegundo
Sigue los últimos estándares RFC para la generación de UUID
Proporciona identificadores ordenables cronológicamente
Previene colisiones en sistemas distribuidos
Este enfoque es más confiable que las implementaciones de UUID personalizadas y elimina la posibilidad de duplicados incluso bajo alta carga.
Dependencias
@modelcontextprotocol/sdk: Para la implementación del servidor MCPuuid: para la generación de UUID que cumple con RFCTypeScript y herramientas relacionadas para el desarrollo
Ejemplo
Cuando se llama, la herramienta devuelve una cadena UUID v7 que se ve así:
018e94d2-279b-7bd3-9289-80d1e6619670La primera parte del UUID contiene la marca de tiempo, lo que hace que estos identificadores se puedan ordenar cronológicamente y al mismo tiempo mantengan el formato UUID estándar.
Available Tools
1 toolgenerateUuidA
Generate a UUID v7 that's timestamp-based and guaranteed to be unique
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool generates a UUID v7 (implying a read-only operation that produces output) and specifies it's 'timestamp-based' and 'guaranteed to be unique', which adds useful behavioral context. However, it doesn't mention potential side effects, error conditions, or performance characteristics, leaving some gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's function and key attributes ('timestamp-based', 'guaranteed to be unique'). It is front-loaded with the core purpose and avoids any unnecessary words, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is nearly complete for its context. It clearly explains what the tool does and key behavioral traits. A minor deduction is made because it doesn't specify the output format or any usage constraints, but overall it's sufficient for a basic generation tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter details, earning a baseline score of 4 for effectively handling a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('Generate') and resource ('UUID v7'), with additional specificity about it being 'timestamp-based' and 'guaranteed to be unique'. It fully distinguishes what the tool does without any sibling tools to differentiate from.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context through 'timestamp-based' and 'guaranteed to be unique', suggesting it's suitable for scenarios requiring time-ordered unique identifiers. However, it lacks explicit guidance on when to use this tool versus alternatives, and there are no sibling tools mentioned to provide comparative context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose that cannot be confused with any other tool in the set.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'generateUuid' follows a clear verb_noun pattern and stands alone without any conflicting conventions.
A single tool is too few for most practical server purposes, making the set feel thin and limited. While generating UUIDs is a straightforward task, a server with only one tool lacks the breadth typically expected for agent workflows, even for a simple domain like UUID generation.
For the narrow domain of UUID generation, the tool provides the core functionality (generate a UUID v7). However, there are notable gaps, such as no tools for generating other UUID versions (e.g., v4), validating UUIDs, or parsing UUIDs, which limits agent flexibility in handling UUID-related tasks.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
A time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceThis server implements the Model Context Protocol to facilitate meaningful interaction and understanding development between humans and AI through structured tools and progressive interaction patterns.57
- FlicenseDqualityDmaintenanceA simple service that generates random UUIDs when requested through Claude Desktop.1
- AlicenseAqualityDmaintenanceA simple Model Context Protocol server that provides timestamp-based UUID v7 identifiers when called by an LLM, offering chronologically sortable unique IDs with no input parameters needed.1229MIT
- FlicenseNot gradedqualityDmaintenanceGenerates UUIDv7 strings either individually or in batches, providing time-sortable universally unique identifiers through the Model Context Protocol.
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tanker327/uuid-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server