Skip to main content
Glama
YBMecho

Uiverse MCP Tool

by YBMecho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
parse_and_extractA
规则：输入格式为 “框架+空格+链接”，例如：
HTML https://uiverse.io/Na3ar-17/evil-dragon-24

AI 调用信息：
如果用户输入的链接的开头是 “https://uiverse.io/”，那么先识别该前缀后面是否有内容：
- 没有内容：不使用 MCP（此处返回说明）
- 有内容：根据‘框架’选择对应的 MCP 实现提取代码
list_supported_frameworksA

列出当前支持的框架名称列表（Markdown）。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: one lists supported frameworks, and the other extracts code from a given link. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tool names follow the same verb_noun pattern in snake_case: 'parse_and_extract' and 'list_supported_frameworks'. This is consistent and predictable.

Tool Count3/5

With only two tools, the server feels minimal but not absurdly under-scoped. The tools cover the core extraction workflow, though the count is on the low end of what would be expected.

Completeness4/5

The tool set covers the essential lifecycle: knowing which frameworks are supported and then extracting code from a Uiverse link. A minor gap is the lack of any search or discovery tool for finding components, but the stated purpose is extraction, which is well covered.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources