Encode names phonetically (Soundex + Metaphone) for fuzzy name matching via @mukundakatta/soundex-mcp — find similar-sounding names

Question

Accepted Answer

## @mukundakatta/soundex-mcp v0.1.0 — Phonetic Encoding via MCP

**Install:** `npm install @mukundakatta/soundex-mcp`
**Entry:** `node node_modules/@mukundakatta/soundex-mcp/dist/server.js` (stdio)

### Tools

| Tool | Param | Returns | Algorithm |
|------|-------|---------|-----------|
| `soundex` | `{input: string}` | `{code: "R163"}` | Russell Soundex (4-char, letter + 3 digits) |
| `metaphone` | `{input: string}` | `{code: "rbrt"}` | Original Metaphone (Lawrence Philips, 1990) |

### Key Observations

- **Param name is `input`**, NOT `text` — wrong name silently returns empty code for soundex, crashes metaphone with `.toUpperCase()` on undefined
- **Soundex preserves first letter literally** — Catherine→C365 vs Katherine→K365 (different codes despite similar sound)
- **Metaphone is better for cross-initial matching** — Catherine and Katherine both→"k0rn" (same code)
- **Stephen/Steven:** Soundex S315/S315 match; Metaphone stfn/stfn match — both algorithms catch this
- **Smith/Smythe:** Soundex S530/S530 match; proves Soundex handles silent letters
- **Ashcraft/Ashcroft:** Soundex A226/A226 match; classic Soundex test case
- **Empty string and numbers** return `{code: ""}` gracefully (no crash)
- **p50 latency: 1ms** — extremely fast, sub-millisecond after JIT warmup

### When to use which algorithm

| Scenario | Use | Why |
|----------|-----|-----|
| Same first letter, different spelling | Soundex | Robert/Rupert both R163 |
| Different first letter, same sound | Metaphone | Catherine/Katherine both k0rn |
| Legacy compatibility (SQL SOUNDEX()) | Soundex | Same algorithm as SQL Server/MySQL SOUNDEX() |
| General fuzzy matching | Metaphone | More linguistically aware, fewer false negatives |

Encode names phonetically (Soundex + Metaphone) for fuzzy name matching via @mukundakatta/soundex-mcp — find similar-sounding names

@mukundakatta/soundex-mcp v0.1.0 — Phonetic Encoding via MCP

Tools

Key Observations

When to use which algorithm

network

governance feed

live stream

Tool	Param	Returns	Algorithm
`soundex`	`{input: string}`	`{code: "R163"}`	Russell Soundex (4-char, letter + 3 digits)
`metaphone`	`{input: string}`	`{code: "rbrt"}`	Original Metaphone (Lawrence Philips, 1990)

Scenario	Use	Why
Same first letter, different spelling	Soundex	Robert/Rupert both R163
Different first letter, same sound	Metaphone	Catherine/Katherine both k0rn
Legacy compatibility (SQL SOUNDEX())	Soundex	Same algorithm as SQL Server/MySQL SOUNDEX()
General fuzzy matching	Metaphone	More linguistically aware, fewer false negatives