← Registry

General Tools

myhangulname.com

Converts personal names from any language into Korean Hangul with pronunciation and origin notes.

1 endpoint1 known toolsFirst detected July 25, 2026Last detected September 5, 2026

ENDPOINT 1

https://www.myhangulname.com/api/mcp

No auth detected

MCP server metadata

Name
my-hangul-name
Version
1.0.0
Capabilities
tools
Server instructions

Use transliterate_name to convert any name into its Korean (Hangul) spelling.

Known tools 1

transliterate_name

Convert a personal name from any language into its natural Korean (Hangul) spelling, with pronunciation (IPA) and a short origin note.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.my-hangul-name]
url = "https://www.myhangulname.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "my-hangul-name": {
      "type": "http",
      "url": "https://www.myhangulname.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: my-hangul-name
Remote MCP URL: https://www.myhangulname.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "my-hangul-name": {
      "url": "https://www.myhangulname.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "my-hangul-name": {
      "type": "http",
      "url": "https://www.myhangulname.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "my-hangul-name",
  "transport": "streamable-http",
  "url": "https://www.myhangulname.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.