Remote MCP · Endpoint

WIHP: foreign text to Hangul MCP server

No. WIHP: foreign text to Hangul answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://mcp-wihp.wiastandards.com/mcp

The last check completed an MCP handshake.

Registry name
com.wiastandards/wihp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
525 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Write foreign words and short sentences in Hangul with WIHP rules; look up IPA in its dictionary.
Listing
From the official MCP registry (active).
Recent checks of WIHP: foreign text to Hangul
CheckedResultHandshake
13 minutes agoHandshake completed525 ms
9 days agoHandshake completed464 ms
9 days agoHandshake completed478 ms
11 days agoHandshake completed495 ms
12 days agoHandshake completed468 ms
13 days agoHandshake completed479 ms
14 days agoHandshake completed461 ms
15 days agoHandshake completed486 ms
16 days agoHandshake completed460 ms
19 days agoHandshake completed462 ms
21 days agoHandshake completed471 ms
24 days agoHandshake completed456 ms
26 days agoHandshake completed544 ms
28 days agoHandshake completed508 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with WIHP: foreign text to Hangul and makes no claim about it beyond what these checks measured.