Skip to content
Gender API logo

Gender API MCP server

Predict the gender of a person based on their name using Gender-api service.

Gender API is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
4
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the Gender API MCP server

Connect Gender API once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Gender API and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Gender API tools your AI can run

Once connected, your assistant can call any of these Gender API actions by asking in plain language.

  • Get Gender by First Name

    Predict the gender of a person based on their first name

    3 fields

  • Get Gender by Full Name

    Predict the gender of a person based on their full name

    3 fields

  • Get Statistics

    Get account statistics including remaining credits and usage information

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Give your assistant Gender API

Connect Gender API once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Gender API MCP, answered.

No. That is the point of it. One Activepieces server exposes Gender API alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Gender API in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 4 tools, including Get Gender by First Name, Get Gender by Full Name, Get Statistics, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.