GenderAPI.io MCP server
6 operations0 webhooks
Infer gender from a name, an email address or a username with GenderAPI.io - one at a time or in a batch of up to 50, with the confidence, the source that answered and the credits it cost.
Try GenderAPI.io with your agent
Connect GenderAPI.io, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in GenderAPI.io on my account, then run one read-only example and show me the result.
GenderAPI.io tools and triggers
Tools are what your agent can do in GenderAPI.io through Corsair's MCP server. Triggers are the GenderAPI.io events a routine can start from.
Account
- CapabilitiesRead-only
Read the deployment version, the AI availability and the batch limit. This route is free
account.capabilities
- Error CatalogRead-only
Read every error code with the statuses it uses and what a caller should do about it. This route is free
account.errorCatalog
- UsageRead-only
Read the shared balance, the trial reset time and whether this call used a key or the IP trial. This route is free
account.usage
Gender
- BatchRead-only
Infer gender for up to 50 names, emails or usernames in one request. An item can fail on its own, and only successful items are billed
gender.batch
- InferRead-only
Infer gender from a name, an email address or a username, with a confidence, the source that answered (dataset or AI) and the credits it cost
gender.infer
Phone
- ValidateRead-only
Validate and format a phone number, returning its E.164 form, country and calling code
phone.validate
Connect GenderAPI.io to Claude, ChatGPT or Cursor
- 1
Connect GenderAPI.io in Corsair
Add your GenderAPI.io API key once in Corsair. Corsair stores the credential encrypted and makes the GenderAPI.io API calls for your agent, so it never goes into a prompt or a config file. Connect GenderAPI.io
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs GenderAPI.io. On a ChatGPT personal plan, connect GenderAPI.io here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. Every GenderAPI.io operation only reads data, so it runs right away in every mode.
FAQ
Install corsair and @corsair-dev/genderapiio, add the GenderAPI.io plugin, and connect with an API key. Then call methods like corsair.genderapiio.api.account.capabilities() from your app. Corsair keeps each tenant isolated.
Yes. GenderAPI.io requires an API key from your GenderAPI.io account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit GenderAPI.io, GitHub, Notion, Stripe, and the rest. Trigger GenderAPI.io from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for infer gender from a name, an email address or a username with GenderAPI.io - one at a time or in a batch of up to 50, with the confidence, the source that answered and the credits it cost. Common builds include sync jobs, admin tooling, and agents that call GenderAPI.io APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per GenderAPI.io API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/genderapiio in the open repo. When GenderAPI.io ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your GenderAPI.io data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store GenderAPI.io data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put GenderAPI.io on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every GenderAPI.io operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.