Skip to main content
Glama
enesjakozh
aki-kii

MCP UUID Server

by aki-kii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

MCP UUID サーバー

概要

このMCPサーバーは、UUIDを生成するためのシンプルなサービスを提供します。

Related MCP server: UUID MCP Provider

環境要件

  • Python 3.10以上

  • MCP(Model Context Protocol)パッケージ v1.2.0以上

  • Claude Desktop

インストール方法

# 依存関係のインストール
uv pip sync

使用方法

1. Claude Desktopでの使用

設定ファイルの編集

Claude Desktopの設定ファイルを編集して、このMCPサーバーを追加します。設定ファイルのパスは以下の通りです：

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

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

以下のJSON設定を追加します（既存のmcpServersオブジェクト内に追加）：

{
  "mcpServers": {
    "uuid": {
      "command": "/path/to/uv",
      "args": [
          "--directory",
          "/path/to/mcp-uuid",
          "run",
          "get-uuid.py"
      ]
    }
  }
}

注意: /path/to/uvには、uvコマンドの絶対パスを指定してください。

2. 使用可能なツール

このMCPサーバーは以下のツールを提供します：

get_uuid

  • 説明：新しいUUIDを生成します

  • 入力パラメータ：なし

  • 使用例：

Claude Desktopで以下のように入力することで、新しいUUIDを生成できます：

ランダムなIDを生成してください

すると、Claudeは内部的にMCPツールを呼び出し、新しいUUIDを生成して返します。

生成されたランダムなIDは次の通りです： eccf34af-1617-4f61-b148-e900bc1d3d00

Available Tools

1 tool
get_uuidD
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedget_uuid
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_uuid' has a clear, distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming follows a consistent verb_noun pattern with 'get_uuid'. Since there is only one tool, there is no inconsistency or mixing of conventions to evaluate.

Tool Count2/5

A single tool for a UUID server feels thin and limited in scope. While it might serve a basic purpose, it lacks the depth expected for a server that could offer more functionality such as generating multiple UUIDs, validating UUIDs, or handling different UUID versions.

Completeness1/5

The tool surface is severely incomplete for a UUID domain. It only provides a 'get' operation, missing essential functions like generating UUIDs with specific versions, validating UUID formats, or converting between UUID representations, which are common in UUID libraries.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • UUID MCP Provider

    tanker327
    A
    license
    A
    quality
    D
    maintenance
    A simple Model Context Protocol server that generates timestamp-based UUIDs (v7) when called by an LLM, providing chronologically sortable unique identifiers with no input parameters needed.
    1
    237 npm
    1
    MIT

  • 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
    237 npm
    MIT

  • unique-id-generator

    Pyroxin
    A
    license
    Not graded
    quality
    D
    maintenance
    A simple MCP server that provides tools for generating unique IDs in several formats, useful for when you need an LLM to create data containing new IDs.
    Eclipse Public 2.0

  • mcp-uuid

    conao3
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that generates random UUIDs (v4) for MCP-compatible clients like Claude Desktop.
    2
    Apache 2.0

Appeared in Searches