Skip to main content
Glama
enesjakozh
tanker327

UUID MCP Provider

by tanker327
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

UUID MCP 提供程序

一个简单的模型上下文协议 (MCP) 服务器，每当 LLM 调用它时，它都会提供基于时间戳的 UUID。

特征

  • 提供单一工具： generateUuid

  • 使用 UUID v7 作为基于时间戳的唯一标识符

  • 界面简单，无需输入参数

  • 轻松与 Claude 和其他 LLM 整合

Related MCP server: MCP UUID Server

安装

# Install dependencies
npm install

# Build the project
npm run build

用法

您可以直接运行服务器：

npm start

与 Claude Desktop 集成

要与 Claude Desktop 集成，请将其添加到您的 Claude Desktop 配置文件中：

  • macOS： ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows： %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "uuid-provider": {
      "command": "node",
      "args": ["/absolute/path/to/uuid-mcp/build/index.js"]
    }
  }
}

将/absolute/path/to/uuid-mcp/build/index.js替换为您构建的 index.js 文件的绝对路径。

更新配置后，重新启动Claude Desktop即可看到可用的UUID生成工具。

工作原理

此服务器使用官方uuid包生成 UUID v7 标识符。UUID v7 专门设计为基于时间戳，同时保持强大的唯一性保证：

  • 包含毫秒精度的 Unix 时间戳

  • 添加随机数据以确保即使在同一毫秒内生成多个 ID 也能保持唯一性

  • 遵循最新的 UUID 生成 RFC 标准

  • 提供按时间顺序排序的标识符

  • 防止分布式系统中的碰撞

这种方法比自定义 UUID 实现更可靠，即使在高负载下也能消除重复的可能性。

依赖项

  • @modelcontextprotocol/sdk ：用于 MCP 服务器实现

  • uuid ：用于符合 RFC 标准的 UUID 生成

  • TypeScript 和相关开发工具

例子

调用时，该工具返回一个如下所示的 UUID v7 字符串：

018e94d2-279b-7bd3-9289-80d1e6619670

UUID 的第一部分包含时间戳，使得这些标识符可以按时间顺序排序，同时仍保持标准 UUID 格式。

Available Tools

1 tool
generateUuidA

Generate a UUID v7 that's timestamp-based and guaranteed to be unique

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4/5.0
Behavior3/5

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.

Conciseness5/5

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.

Completeness4/5

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.

Parameters4/5

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.

Purpose5/5

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.

Usage Guidelines3/5

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.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness3/5

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

ActivityInactive
ResponsivenessNo issues

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

Related MCP Servers

  • MCP UUID Server

    aki-kii
    F
    license
    D
    quality
    D
    maintenance
    A simple service that generates random UUIDs when requested through Claude Desktop.
    1

  • UUID MCP Provider

    prazedotid
    A
    license
    A
    quality
    D
    maintenance
    A 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.
    1
    229
    MIT

  • UUIDv7 Generator

    pomazanbohdan
    F
    license
    Not graded
    quality
    D
    maintenance
    Generates UUIDv7 strings either individually or in batches, providing time-sortable universally unique identifiers through the Model Context Protocol.

Appeared in Searches

Latest Blog Posts

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