MCP server

The Nationalize MCP server lets an MCP-compatible client predict nationality from a name as part of a model conversation. Add the endpoint to your client config, paste your API key, and the model can call `predict_nationality` directly.

Endpoint

https://mcp.nationalize.io

The server speaks the standard MCP HTTP transport. Any client that supports remote MCP servers can connect.

Authentication

The MCP server uses your existing API key. Get a key from your account dashboard. Send the key as a bearer token in the Authorization header:

URL:    https://mcp.nationalize.io
Header: Authorization: Bearer YOUR_API_KEY

The exact way to add the header depends on your MCP client. Most clients accept a headers map alongside the server URL — see the per-client pages below for the right shape.

Tool surface

The server exposes one tool:

Tool	Parameters	Returns
`predict_nationality`	name (string, required)	`{ country, count }`

country is an array of up to five candidates ordered by descending probability — each entry has a two-letter ISO 3166-1 alpha-2 country_id and a probability between 0 and 1.

The model picks the tool when the conversation calls for nationality prediction. You do not invoke it directly; the client handles routing.

Rate limits and quota

MCP requests count against your monthly quota — same plan, same cap. One predict_nationality call equals one name, deducted from your plan's monthly allowance. See pricing for tier details.

Rate-limit headers from the underlying API are surfaced through the MCP transport when supported by the client.

Set up your client

Claude Code

One-line CLI install. Set up the Nationalize MCP server in Claude Code.

Other MCP-compatible clients — Claude Desktop, Cursor, ChatGPT, Cline, Continue, Windsurf, Zed — can connect to the same endpoint with the same bearer-token header. Per-client setup guides are coming soon.

Use it for the other services too

The Demografix MCP servers are split per service — one endpoint per dimension, all keyed by the same API key. Add all three to your client to predict gender, age, and nationality from the same conversation.

{
  "mcpServers": {
    "genderize": {
      "url": "https://mcp.genderize.io",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    },
    "agify": {
      "url": "https://mcp.agify.io",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    },
    "nationalize": {
      "url": "https://mcp.nationalize.io",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Per-service docs: genderize.io/documentation/mcp · agify.io/documentation/mcp · nationalize.io/documentation/mcp