
Wraps the nationalize.io API to predict nationality from first names without requiring authentication. You get a single prediction endpoint that returns probable countries with confidence scores. Useful when you need quick demographic inference for name data in CRM cleanup, form validation, or user research. Part of the Pipeworx gateway, so you can either connect to this standalone server or access it through their unified gateway alongside 250+ other data sources. The ask_pipeworx wrapper lets you query in natural language instead of calling tools directly. Free tier available, no API keys needed.
Nationalize MCP — nationality prediction from first name (nationalize.io, free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
predict_nationality | Predict likely nationalities from a first name. Returns up to 5 country codes ranked by probability (0.0–1.0). Use when inferring someone's origin from their given name. |
batch_predict | Predict nationalities for multiple first names at once (up to 10). Returns country codes with probability scores for each name. Use to process name lists efficiently. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"nationalize": {
"url": "https://gateway.pipeworx.io/nationalize/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/nationalize/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Nationalize data" })
The gateway picks the right tool and fills the arguments automatically.
MIT