# GlyphGuard (remote · glyphguard.mike-tusa.workers.dev)

Find hidden Unicode (zero-width, bidi, tag payloads), homoglyphs and lookalike names in text.

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

## Components

- remote · `glyphguard.mike-tusa.workers.dev`: 79/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mike-tusa-glyphguard-glyphguard/glyphguard.md), [page](https://verifymcp.io/servers/dev-workers-mike-tusa-glyphguard-glyphguard/glyphguard)

## Channel facts

- Endpoint: `https://glyphguard.mike-tusa.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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**: 63/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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 799 tokens (~266/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 GlyphGuard MCP server?

GlyphGuard is a hosted endpoint at https://glyphguard.mike-tusa.workers.dev/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 dev-workers-mike-tusa-glyphguard-glyphguard 'https://glyphguard.mike-tusa.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-glyphguard-glyphguard": {
      "url": "https://glyphguard.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mike-tusa-glyphguard-glyphguard": {
      "type": "http",
      "url": "https://glyphguard.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mike-tusa-glyphguard-glyphguard]
url = "https://glyphguard.mike-tusa.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mike-tusa-glyphguard-glyphguard": {
      "type": "remote",
      "url": "https://glyphguard.mike-tusa.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mike-tusa-glyphguard-glyphguard --url 'https://glyphguard.mike-tusa.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mike-tusa-glyphguard-glyphguard:
    url: "https://glyphguard.mike-tusa.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mike-tusa-glyphguard-glyphguard": {
      "Transport": "http",
      "Url": "https://glyphguard.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mike-tusa-glyphguard-glyphguard -t streamable-http -u 'https://glyphguard.mike-tusa.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-glyphguard-glyphguard": {
      "type": "http",
      "url": "https://glyphguard.mike-tusa.workers.dev/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-21 (score 79, +1)

- [security] Stability: 0.97 → pass

### 2026-11-18 (score 78, +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-11-16 (score 77, +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-11-14 (score 76, +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-11-12 (score 75, +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-11-10 (score 74, +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-11-08 (score 73, +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-11-06 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `scan_text` (~155 tokens)

Scan text for hidden or deceptive Unicode

Find invisible characters, bidi controls (Trojan Source), hidden Unicode tag payloads (decoded), variation-selector runs, control characters, unusual spaces, mixed-script words and lookalike letters. ZWJ/ZWNJ/VS16 in legitimate context (emoji sequences, Persian/Arabic joining, Indic virama) are reported as info joiner_in_context and do not raise risk; elsewhere they stay medium. Lone surrogates are flagged. Returns a risk level (none/low/medium/high), counts, and findings with UTF-16 offsets and code points. Read-only. Same engine as GET /api/scan.

Input parameters:

- `text` (string, required): Text to inspect (up to 2000 UTF-16 code units).

Output parameters:

- `codePoints` (integer)
- `counts` (object)
- `findings` (array)
- `length` (integer)
- `normalizedNfkcDiffers` (boolean)
- `notes` (array)
- `risk` (string)
- `tagPayload` (string)
- `total` (integer)
- `truncated` (boolean)
- `version` (string)

### `clean_text` (~293 tokens)

Remove hidden Unicode from text

Return the text with invisible characters, bidi controls, tag characters and control characters removed and unusual spaces turned into normal spaces. By default ZWJ/ZWNJ/VS16 are kept inside emoji sequences, between letters of joining scripts (Arabic, Persian) and after an Indic virama (keep_joiners=true); strict=true removes them everywhere. Optional: map lookalike letters to Latin (lookalikes) and apply NFKC normalisation (nfkc). Read-only. Same engine as GET /api/clean.

Input parameters:

- `keep_joiners` (boolean): Keep ZWJ/ZWNJ/VS16 where they are legitimate: emoji ZWJ sequences and VS16 emoji presentation, between letters of joining scripts (Arabic, Persian), and after an Indic virama. Joiners elsewhere are a…
- `lookalikes` (boolean): Map lookalike letters (e.g. Cyrillic а) to Latin. Changes legitimate non-Latin text too.
- `nfkc` (boolean): Apply Unicode NFKC first (fullwidth and math letters → plain).
- `spaces` (boolean): Turn unusual spaces into a normal space.
- `strict` (boolean): Strict mode: remove every joiner and variation selector, even in emoji and Persian/Indic text (overrides keep_joiners).
- `text` (string, required): Text to inspect (up to 2000 UTF-16 code units).

Output parameters:

- `changed` (boolean)
- `joinersKept` (integer)
- `length` (integer)
- `lookalikesMapped` (integer)
- `notes` (array)
- `options` (object)
- `removed` (object)
- `text` (string)
- `version` (string)

### `compare_names` (~112 tokens)

Check a name for lookalike impersonation

Check whether a name, username, domain label or brand looks the same as any of up to 50 protected names (for example "pаypal" with a Cyrillic а vs "paypal"), using a UTS #39-style confusable skeleton (curated subset, case and accents ignored). Read-only. Same engine as GET /api/compare.

Input parameters:

- `name` (string, required): Name, username, domain label or brand to test.
- `targets` (array, required): 1 to 50 protected names.

Output parameters:

- `confusableWith` (array)
- `name` (string)
- `nameRisk` (string)
- `nameScripts` (array)
- `notes` (array)
- `results` (array)
- `skeleton` (string)
- `version` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65

## Common questions

### What is the GlyphGuard MCP server?

GlyphGuard is an MCP server listed in the public MCP registry as dev.workers.mike-tusa.glyphguard/glyphguard. Find hidden Unicode (zero-width, bidi, tag payloads), homoglyphs and lookalike names in text. This page covers its hosted endpoint (https://glyphguard.mike-tusa.workers.dev/mcp).

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

GlyphGuard scores 79 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 GlyphGuard MCP server expose?

GlyphGuard exposes 3 tools: scan_text, clean_text, compare_names. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Does the GlyphGuard MCP server require authentication?

No. We connected to GlyphGuard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GlyphGuard MCP server still maintained?

GlyphGuard 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 GlyphGuard MCP server?

VerifyMCP ran 12 checks on GlyphGuard, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about GlyphGuard: HTTPS. 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://glyphguard.mike-tusa.workers.dev/mcp
- Website: https://glyphguard.mike-tusa.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mike-tusa-glyphguard-glyphguard/glyphguard.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mike-tusa-glyphguard-glyphguard/glyphguard/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-workers-mike-tusa-glyphguard-glyphguard/glyphguard.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mike-tusa-glyphguard-glyphguard/glyphguard
