# Tseha (remote · tseha.io)

Serves your design system and coding standards to coding agents, so they stop guessing.

- Trust score: 92/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `tseha.io`: 92/100 (this document), [markdown](https://verifymcp.io/servers/io-tseha-tseha/tseha.md), [page](https://verifymcp.io/servers/io-tseha-tseha/tseha)

## Channel facts

- Endpoint: `https://tseha.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2502 tokens (~278/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Tseha MCP server?

Tseha is a hosted endpoint at https://tseha.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-tseha-tseha 'https://tseha.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-tseha-tseha": {
      "url": "https://tseha.io/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.io-tseha-tseha]
url = "https://tseha.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tseha-tseha": {
      "type": "remote",
      "url": "https://tseha.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-tseha-tseha --url 'https://tseha.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-tseha-tseha:
    url: "https://tseha.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-tseha-tseha": {
      "Transport": "http",
      "Url": "https://tseha.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-tseha-tseha -t streamable-http -u 'https://tseha.io/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `list_projects` (~97 tokens)

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 credential may see. Call it first in a session: the returned id is the project_id that every other tool in this server requires, and guessing that id fails. It does not return components, packages, or tokens - use list_components, list_packages, or get_style_tokens for those.

### `list_packages` (~225 tokens)

List component 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 which npm package to import from, or to read the installed version before calling get_component_updates. It lists packages, not their contents - use list_components to enumerate components and get_component for one component API. project_id is the only argument and it does more than filter output: assignment and active-package status are per project, so one organization package can be listed as active here and absent from a sibling project.

Input parameters:

- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…

### `list_components` (~252 tokens)

List UI 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 unpaginated: it returns the whole catalog across all packages assigned to the project, so expect a large response on big design systems. Use it to see what exists before building UI, and to get the exact component name other tools need. Do not use it to find a component by need - search_components ranks by description - and do not use it for props, examples, or Figma data, which only get_component returns. project_id is not a display filter: it selects the assigned packages, so two projects in one organization legitimately return different catalogs.

Input parameters:

- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…

### `get_component` (~295 tokens)

Get component spec

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, and dependencies. Read-only. Call it before writing code that uses a component, so props and import path come from the design system instead of memory. The name argument must be the exact component name as returned by list_components or search_components (case-sensitive, no package prefix); an unknown name returns a not-found error rather than a near match, so resolve the name first with search_components if you are guessing. The result may carry a provenance warning when the record was LLM-generated and not yet reviewed - treat those fields as unverified. It covers one component at a time; use list_components to enumerate and get_component_updates for version-to-version changes.

Input parameters:

- `name` (string, required): Exact component name, e.g. "Button"
- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…

### `search_components` (~317 tokens)

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 score. Read-only. Use it when you can describe what the UI must do but do not know the component name. The query is free-text describing the need, such as "date range picker" or "dismissible inline warning" - not a component name, not a glob, and not a props expression. Do not use it when the exact name is known (get_component is direct and returns the full spec) or when you want the complete catalog (list_components). Semantic ranking needs AI features on the Team plan or above; on other plans it falls back to name and import-path matching and the score is null. No close match returns an empty result list, not an error.

Input parameters:

- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…
- `query` (string, required): Free-text description of the need - a use case, behavior, or purpose, e.g. "date range picker". Not a component name and not a glob.

### `get_style` (~267 tokens)

Get style metadata

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 color, typography, spacing). Read-only and small - it names categories but returns no token values. Use it to inspect the project theme, or to learn which categories are populated before requesting values; call get_style_tokens for the values themselves. project_id is the only argument and it is not a plain filter: a style is assigned per project and there is no organization-level fallback, so sibling projects can report different style names and different populated categories, and a project with no style assigned returns a null style with a note rather than an error.

Input parameters:

- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…

### `get_style_tokens` (~296 tokens)

Get design 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 hex codes, spacing, or radii. The category argument takes exactly one of: color, typography, spacing, radius, shadow, blur, all; omitting it behaves the same as "all". Pass a single category when you know which one you need - "all" returns the largest response this server produces. Use get_style first if you only need to know which categories exist, and get_standards for coding conventions, which are not tokens. A project with no style configured returns an empty token list with a note, not an error.

Input parameters:

- `category` (string): One of: color, typography, spacing, radius, shadow, blur, all
- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…

### `get_standards` (~313 tokens)

Get development standards

Returns the organization's development standards: coding conventions, project structure, and framework-specific rules. Read-only. Call it before writing or reviewing code, so the result follows this organization's rules rather than general defaults. Call it first without a section to get an index of available sections, each with a note on what it covers, then call again with one section id copied from that index; inventing a section id returns a not-found error naming that step. Request only the sections a task needs - the full content of one section can be long. The framework argument is deprecated: use section with the "framework:" prefix instead. It returns prose rules, not data - use get_style_tokens for visual values and get_component for component APIs.

Input parameters:

- `framework` (string): Deprecated - use section instead. e.g. "react", "nextjs"
- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…
- `section` (string): Section identifier from the index, e.g. "global", "project_structure", "framework:react", "cicd". Omit to get the index.

### `get_component_updates` (~302 tokens)

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 version. Read-only: it reports an upgrade, it never performs one. Use it when planning or reviewing a component-library upgrade, or before bumping the package version in a manifest. current_version is the exact semver currently installed, e.g. "1.0.0" - not a range, so no leading "v", "^", or "~"; read it from list_packages when unsure. Passing the latest version returns an empty change set. It is not a per-component changelog and not a current spec - use get_component for one component today, and list_packages for what is installed. Requires update tracking, a Team plan feature; on lower plans it returns an upgrade-required error instead of data.

Input parameters:

- `current_version` (string, required): The version currently installed, e.g. "1.0.0"
- `project_id` (string, required): UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-tseha-tseha/tseha#diagnostics

## Score history

- 2026-09-20: 92
- 2026-09-19: 92
- 2026-09-18: 91
- 2026-09-17: 91
- 2026-09-16: 90
- 2026-09-15: 90
- 2026-09-14: 89
- 2026-09-13: 89
- 2026-09-12: 88
- 2026-09-11: 88
- 2026-09-10: 87
- 2026-09-09: 87
- 2026-09-08: 86
- 2026-09-07: 86
- 2026-09-06: 86
- 2026-09-05: 85
- 2026-09-04: 85
- 2026-09-03: 84
- 2026-09-02: 84
- 2026-09-01: 83
- 2026-08-31: 83
- 2026-08-30: 82
- 2026-08-29: 82
- 2026-08-28: 81
- 2026-08-27: 81
- 2026-08-26: 80
- 2026-08-25: 78
- 2026-08-24: 78
- 2026-08-23: 74
- 2026-08-22: 36

## Common questions

### What is the Tseha MCP server?

Tseha is an MCP server listed in the public MCP registry as io.tseha/tseha. Serves your design system and coding standards to coding agents, so they stop guessing. This page covers its hosted endpoint (https://tseha.io/mcp).

### Is the Tseha MCP server safe to use?

Tseha scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Tseha MCP server expose?

Tseha exposes 9 tools: list_projects, list_packages, list_components, get_component, search_components, and 4 more. Their descriptions and schemas cost roughly 2,364 tokens of context every time the server is loaded.

### Does the Tseha MCP server require authentication?

Yes. Tseha asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Tseha MCP server still maintained?

Tseha is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tseha.io/mcp
- Repository: https://github.com/MariuszHenn/tseha-mcp
- Website: https://tseha.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-tseha-tseha/tseha.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-tseha-tseha/tseha.json
- HTML version of this page: https://verifymcp.io/servers/io-tseha-tseha/tseha