# Tseha MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.tseha%2Ftseha
Registry id: `mcp-registry/io.tseha/tseha`
Status: live (checked 2026-10-27T04:40:15.686Z)

## Verdict

Tseha MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 1167 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (93/100) across 9 tools, costing an agent about 2,947 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 1167 ms | 14% of MCP servers |
| p95 handshake latency | 3703 ms | — |
| Checks in 30 days | 4,938 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 93/100 (A) | 76% of MCP servers |
| Tools | 9 | — |
| Tool-list size for an agent | ~2,947 tokens | 46% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "tseha-mcp-server": {
      "type": "http",
      "url": "https://tseha.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http tseha-mcp-server https://tseha.io/mcp
```

## Tools (9)

- `get_component`: Returns the full specification for one component: import path, props schema, usage example, anti-patterns, when-to-use and when-not-to-use notes, Figma spec, an
- `get_component_updates`: Returns per-component breaking changes and a migration guide between an installed version of the project's active component package and the latest published ver
- `get_standards`: Returns the organization's development standards: coding conventions, project structure, and framework-specific rules. Read-only. Call it before writing or revi
- `get_style`: Returns metadata for the project's active style: the style name, its Figma file key, when it was last synced, and a token count per available category (such as 
- `get_style_tokens`: Returns the project's design tokens with their names, values, and token paths. Read-only. Use it to source exact visual values for styling instead of inventing 
- `list_components`: Lists every UI component in the project's design system, each with its name, source package, import path, and a short note on its intended use. Read-only and un
- `list_packages`: Lists the component packages assigned to a project, each with its name, version, and description, and marks which one is active. Read-only. Use it to decide whi
- `list_projects`: Lists the projects in this organization, each with its id, name, and framework. Read-only, takes no arguments, and returns only the projects the calling credent
- `search_components`: Searches the components of every package assigned to the project by use case, behavior, or description, and returns up to 10 ranked matches with a relevance sco

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.