
WIA Braille 正音 MCP server
Which MCP servers are WIA Braille 正音's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.wiabraille/wiabrailleverified in the MCP registry
The registry name sits under wiabraille.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools9
- Server calls itselfwiabraille
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 440 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- For "Convert text to braille through its API", the likely first call is braille_convert.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score99 of 100answers 100 · definitions 98 · context 100 · connects 100
- Answered100% of days7 of 7 daily checks
- Median first answer343 ms
- Space in an agent's context≈ 1,404 tokensthe definitions of all its tools (9), which an agent carries on every turn
- Tool definitionsA · 98 of 100
- Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 9
What an agent can do with it
- can do · Convert text to braille through its API
- not sure · Look up IPA pronunciation and grapheme-to-phoneme output
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
braille_convertConverts 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…
braille_languagesLists 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). 한국어: 지원 언어를 목록·검색합니다.
braille_to_brfConverts 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…
braille_verify_brfRuns 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개 항목으로 자동…
braille_math_nemethConverts 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…
braille_engine_infoReturns the WIA Braille engine version and language coverage counts (pronunciation-based, NOT an official national braille code.). 한국어: 엔진 버전과 지원 언어 규모를 보여줍니다.
talk_text_to_gesture_codesReturns 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…
talk_codes_to_textConverts 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…
talk_coverageLists 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 코드가 있는 소리 목록을 보여줍니다.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"wiabraille": {
"type": "http",
"url": "https://mcp.wiabraille.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http wiabraille https://mcp.wiabraille.com/mcpclaude.ai, ChatGPT and other clients: add https://mcp.wiabraille.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.