Remote MCP · Endpoint

WIHP: foreign text to Hangul MCP server

No. WIHP: foreign text to Hangul answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
508 ms
Tools exposed
3 tools
Uptime, last 30 days
3 checks from 3 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
2 hours agoHandshake completed508 ms
2 days agoHandshake completed836 ms
4 days agoHandshake completed495 ms

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

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.