WIA Braille + WIA Talk MCP server
com.wiabraille/wiabraillewiabraille.comstreamable-httpv1.0.0Scanned
Text to WIA Braille (pronunciation-based, not a national code), BRF output and checks, Nemeth math.
9 tools: 5 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 5 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the WIA Braille + WIA Talk MCP server can do
The WIA Braille + WIA Talk MCP server is published by wiabraille.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (5 tools: braille_convert, braille_to_brf, braille_verify_brf, braille_math_nemeth and 1 more), but cannot delete data. 4 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 5 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 5Claude Code: ask
braille_convertConverts text to WIA Braille, a pronunciation-based common braille (NOT an official national braille code).1 finding
Why it is in this group
- The name "braille_convert" says "convert": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "braille_convert" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "braille_convert" says "convert": a word for a change.
Description, as the server wrote it 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 점자로 변환합니다(국가 공식 점자 아님).
Annotations the server declares
- title: Text to WIA Braille (pronunciation-based)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
braille_math_nemethConverts a linear math expression (e.g.1 finding
Why it is in this group
- The description's first verb is "convert": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "braille_math_nemeth" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
Description, as the server wrote it 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. 한국어: 한 줄 수식을 네메스 점자로 변환합니다.
Annotations the server declares
- title: Math text to Nemeth braille (linear expressions)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 co…1 finding
Why it is in this group
- The description's first verb is "convert": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "braille_to_brf" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
Description, as the server wrote it 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 텍스트로 변환합니다.
Annotations the server declares
- title: Braille cells to BRF (embosser file text)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
braille_verify_brfRuns 9 automatic checks on BRF text (mapping, line length, page length, CRLF, form feed, round trip, ...).1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "braille_verify_brf" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
Description, as the server wrote it 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개 항목으로 자동 검증합니다.
Annotations the server declares
- title: Verify BRF text (9 checks)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
talk_codes_to_textConverts WIA Talk ISP codes (e.g.1 finding
Why it is in this group
- The description's first verb is "convert": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "talk_codes_to_text" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
Description, as the server wrote it 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·점자로 되돌립니다.
Annotations the server declares
- title: ISP gesture codes back to IPA / braille
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
braille_engine_infoReturns the WIA Braille engine version and language coverage counts (pronunciation-based, NOT an official national braille code.).No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns the WIA Braille engine version and language coverage counts (pronunciation-based, NOT an official national braille code.). 한국어: 엔진 버전과 지원 언어 규모를 보여줍니다.
Annotations the server declares
- title: Engine version and coverage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
braille_languagesLists or searches the languages the WIA Braille engine can convert (pronunciation-based, NOT an official national braille code.).No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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). 한국어: 지원 언어를 목록·검색합니다.
Annotations the server declares
- title: List / search supported languages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
talk_coverageLists which braille/IPA segments currently have a WIA Talk ISP code.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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 코드가 있는 소리 목록을 보여줍니다.
Annotations the server declares
- title: ISP code coverage list
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
talk_text_to_gesture_codesReturns WIA Talk ISP codes for the SOUNDS of a text (handshape-location-movement-orientation codes).No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.) 한국어: 소리 단위 제스처 코드이며 실제 수어 번역이 아닙니다.
Annotations the server declares
- title: Text to ISP gesture codes (sound-unit codes, not sign language)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.wiabraille.com/mcp: tools/list returned 9 tools to an anonymous client, including braille_convert (write), braille_to_brf (write), braille_verify_brf (write), braille_math_nemeth (write), talk_codes_to_text (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnbraille_convert
The server marks "braille_convert" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "braille_convert" says "convert": a word for a change.
- Warnbraille_to_brf
The server marks "braille_to_brf" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
The server marks "braille_verify_brf" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
The server marks "braille_math_nemeth" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
The server marks "talk_codes_to_text" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wiabraille https://mcp.wiabraille.com/mcpclaude mcp add --transport http wiabraille https://mcp.wiabraille.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__wiabraille__braille_languages",
"mcp__wiabraille__braille_engine_info",
"mcp__wiabraille__talk_text_to_gesture_codes",
"mcp__wiabraille__talk_coverage"
],
"ask": [
"mcp__wiabraille__braille_convert",
"mcp__wiabraille__braille_to_brf",
"mcp__wiabraille__braille_verify_brf",
"mcp__wiabraille__braille_math_nemeth",
"mcp__wiabraille__talk_codes_to_text"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wiabraille. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.wiabraille/wiabraille/verify?hash=0e99f50744167b9edf003ffdc3b277b0f2fe4911557a428d9d0907bd8059e287" | jq -e '.changed == false'Pinned hash 0e99f5074416, from Nov 14, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.wiabraille/wiabraille/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.wiabraille/wiabraille)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
WIA Braille + WIA Talk MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the WIA Braille + WIA Talk MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 5 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the WIA Braille + WIA Talk MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the WIA Braille + WIA Talk MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the WIA Braille + WIA Talk MCP server have?
- 9 tools: 5 write, 4 read. braille_convert, braille_to_brf, braille_verify_brf, braille_math_nemeth, talk_codes_to_text, braille_languages, braille_engine_info, talk_text_to_gesture_codes and 1 more.
Does the WIA Braille + WIA Talk MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the WIA Braille + WIA Talk MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the WIA Braille + WIA Talk MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.