WIA Braille + WIA Talk
REMOTE · MCP.WIABRAILLE.COM
Text to WIA Braille (pronunciation-based, not a national code), BRF output and checks, Nemeth math.
Available components
Last scanned (16 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Education and Research
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1224 tokens (~136/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://mcp.wiabraille.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wiabraille.com | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5775b83a54dee283cdccd57cc11ea0366a6 |
| SANs: *.wiabraille.com, wiabraille.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.wiabraille.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wiabraille.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.wiabraille.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.wiabraille.com/mcp | HTTPS enforced | 301 | https://mcp.wiabraille.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
braille_convert Text to WIA Braille (pronunciation-based) ~162
Converts text to WIA Braille, a pronunciation-based common braille (NOT an official national braille code). Returns IPA and braille cells (6-dot paper form or 8-dot canonical form), plus quality/confidence. Low-quality results are flagged, not hidden. 한국어: 텍스트를 발음 기반 WIA 점자로 변환합니다(국가 공식 점자 아님).
| Name | Type | Req | Description |
|---|---|---|---|
| dots | – | – | 6-dot paper form (default) or 8-dot canonical form |
| lang | string | – | ISO language code, e.g. ko, en, ja. If omitted the API auto-detects; call braille_languages for supported codes |
| text | string | yes | Text to convert (max 5,000 chars) |
No output schema declared.
No examples provided.
braille_engine_info Engine version and coverage ~53
Returns the WIA Braille engine version and language coverage counts (pronunciation-based, NOT an official national braille code.). 한국어: 엔진 버전과 지원 언어 규모를 보여줍니다.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
braille_languages List / search supported languages ~94
Lists or searches the languages the WIA Braille engine can convert (pronunciation-based, NOT an official national braille code.). Shows the conversion sources per language (rules, dictionary, espeak). 한국어: 지원 언어를 목록·검색합니다.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max entries returned (default 50) |
| query | string | – | Language code or name fragment, e.g. korean, ko |
No output schema declared.
No examples provided.
braille_math_nemeth Math text to Nemeth braille (linear expressions) ~104
Converts a linear math expression (e.g. x^2+1=5) to Nemeth-code braille cells. Note the surrounding engine is pronunciation-based, NOT an official national braille code. Best for linear expressions; complex 2D layouts need reviewer post-processing. 한국어: 한 줄 수식을 네메스 점자로 변환합니다.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Math expression, e.g. x^2+1=5 |
No output schema declared.
No examples provided.
braille_to_brf Braille cells to BRF (embosser file text) ~144
Converts Unicode braille cells to BRF (NABCC 6-dot ASCII braille, the text format embossers read), with line/page wrapping (pronunciation-based, NOT an official national braille code.). 8-dot cells are converted to 6-dot by the engine and reported. 한국어: 유니코드 점자를 엠보서용 BRF 텍스트로 변환합니다.
| Name | Type | Req | Description |
|---|---|---|---|
| braille | string | yes | Unicode braille cells (U+2800..) |
| cellsPerLine | integer | – | Cells per line (default 40) |
| linesPerPage | integer | – | Lines per page (default 25) |
No output schema declared.
No examples provided.
braille_verify_brf Verify BRF text (9 checks) ~96
Runs 9 automatic checks on BRF text (mapping, line length, page length, CRLF, form feed, round trip, ...). Does not check paper quality or dot depth (pronunciation-based, NOT an official national braille code.). 한국어: BRF 텍스트를 9개 항목으로 자동 검증합니다.
| Name | Type | Req | Description |
|---|---|---|---|
| brf | string | yes | BRF text (ASCII braille) |
No output schema declared.
No examples provided.
talk_codes_to_text ISP gesture codes back to IPA / braille ~155
Converts WIA Talk ISP codes (e.g. HS02-LC07-MV01-OR03-MM07) back to IPA and WIA Braille. Unknown codes are listed as missing, never invented. Sound-unit codes, not sign language. (pronunciation-based, NOT an official national braille code.) 한국어: ISP 코드를 IPA·점자로 되돌립니다.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | yes | ISP codes such as HS02-LC07-MV01-OR03-MM07; " " marks a word boundary |
| lang | string | – | ISO language code, e.g. ko, en, ja. If omitted the API auto-detects; call braille_languages for supported codes |
No output schema declared.
No examples provided.
talk_coverage ISP code coverage list ~62
Lists which braille/IPA segments currently have a WIA Talk ISP code. Sound-unit codes, not sign language. (pronunciation-based, NOT an official national braille code.) 한국어: ISP 코드가 있는 소리 목록을 보여줍니다.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talk_text_to_gesture_codes Text to ISP gesture codes (sound-unit codes, not sign language) ~148
Returns WIA Talk ISP codes for the SOUNDS of a text (handshape-location-movement-orientation codes). These are sound-unit codes, NOT a translation into any real sign language such as KSL or ASL. Underlying text-to-IPA is pronunciation-based WIA Braille (pronunciation-based, NOT an official national braille code.) 한국어: 소리 단위 제스처 코드이며 실제 수어 번역이 아닙니다.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | ISO language code, e.g. ko, en, ja. If omitted the API auto-detects; call braille_languages for supported codes |
| text | string | yes | – |
No output schema declared.
No examples provided.
How do I install the WIA Braille + WIA Talk MCP server?
WIA Braille + WIA Talk is a hosted endpoint at https://mcp.wiabraille.com/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.
remote · mcp.wiabraille.com
claude mcp add --transport http com-wiabraille-wiabraille 'https://mcp.wiabraille.com/mcp'
What is the WIA Braille + WIA Talk MCP server?
WIA Braille + WIA Talk is an MCP server listed in the public MCP registry as com.wiabraille/wiabraille. Text to WIA Braille (pronunciation-based, not a national code), BRF output and checks, Nemeth math. This page covers its hosted endpoint (https://mcp.wiabraille.com/mcp).
Is the WIA Braille + WIA Talk MCP server safe to use?
WIA Braille + WIA Talk scores 72 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 WIA Braille + WIA Talk MCP server expose?
WIA Braille + WIA Talk exposes 9 tools: braille_convert, braille_languages, braille_to_brf, braille_verify_brf, braille_math_nemeth, and 4 more. Their descriptions and schemas cost roughly 1,018 tokens of context every time the server is loaded.
Does the WIA Braille + WIA Talk MCP server require authentication?
No. We connected to WIA Braille + WIA Talk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WIA Braille + WIA Talk MCP server still maintained?
WIA Braille + WIA Talk is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.