# bitg — new Uzbek alphabet (remote · bitg.uz)

Convert Uzbek text to the new 2026 Latin alphabet (Ö Ğ Ş Ç) from old Latin or Cyrillic.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://bitg.uz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## 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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 280 tokens (~280/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 bitg — new Uzbek alphabet MCP server?

bitg — new Uzbek alphabet is a hosted endpoint at https://bitg.uz/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 uz-bitg-bitg 'https://bitg.uz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "uz-bitg-bitg": {
      "url": "https://bitg.uz/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.uz-bitg-bitg]
url = "https://bitg.uz/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add uz-bitg-bitg --url 'https://bitg.uz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uz-bitg-bitg:
    url: "https://bitg.uz/mcp"
```

### Netclaw

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

### Vellum

```bash
assistant mcp add uz-bitg-bitg -t streamable-http -u 'https://bitg.uz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "uz-bitg-bitg": {
      "type": "http",
      "url": "https://bitg.uz/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-11-20 (score 76, +1)

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

### 2026-11-18 (score 75, +1)

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

### 2026-11-17 (score 74, +1)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-16 (score 73, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-14 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28

### 2026-11-13 (score 72)

First indexed and scored.

## MCP tools (1)

### `convert_text` (~219 tokens)

Convert Uzbek text to the new alphabet (bitg)

Converts Uzbek text written in the old Latin alphabet (o‘ g‘ sh ch, any apostrophe) or in Cyrillic to the official new Uzbek Latin alphabet adopted in 2026 (Ö ö, Ğ ğ, Ş ş, Ç ç; law in force from 2027-04-22). Deterministic, rule-based bitg engine: keeps English words, links, code and foreign names intact. Use it whenever the user asks to write, convert or check Uzbek text in the new alphabet; also converts back to the old Latin alphabet or to Cyrillic.

Input parameters:

- `direction` (string): to_new: old Latin or Cyrillic -> new 2026 alphabet (default). to_old: new -> old Latin (oʻ gʻ). to_cyrillic: Latin -> Uzbek Cyrillic.
- `old_style` (string): Only for to_old: official uses oʻ gʻ (U+02BB), ascii uses o' g'.
- `text` (string, required): Uzbek text, up to 20000 characters.

Output parameters:

- `converted_by` (string)
- `direction` (string)
- `text` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 73
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72

## Common questions

### What is the bitg — new Uzbek alphabet MCP server?

bitg — new Uzbek alphabet is an MCP server listed in the public MCP registry as uz.bitg/bitg. Convert Uzbek text to the new 2026 Latin alphabet (Ö Ğ Ş Ç) from old Latin or Cyrillic. This page covers its hosted endpoint (https://bitg.uz/mcp).

### Is the bitg — new Uzbek alphabet MCP server safe to use?

bitg — new Uzbek alphabet scores 76 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 bitg — new Uzbek alphabet MCP server expose?

bitg — new Uzbek alphabet exposes 1 tool: convert_text. Their descriptions and schemas cost roughly 219 tokens of context every time the server is loaded.

### Does the bitg — new Uzbek alphabet MCP server require authentication?

No. We connected to bitg — new Uzbek alphabet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the bitg — new Uzbek alphabet MCP server still maintained?

bitg — new Uzbek alphabet is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the bitg — new Uzbek alphabet MCP server?

VerifyMCP ran 13 checks on bitg — new Uzbek alphabet, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://bitg.uz/mcp
- Repository: https://github.com/dtwinuz/bitg
- Website: https://bitg.uz/
- Changelog RSS feed: https://verifymcp.io/servers/uz-bitg-bitg/bitg.xml
- Changelog JSON feed: https://verifymcp.io/servers/uz-bitg-bitg/bitg/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uz-bitg-bitg/bitg.json
- HTML version of this page: https://verifymcp.io/servers/uz-bitg-bitg/bitg
