Genderize MCP — gender prediction from first name (genderize.io, free, no auth)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 33 tools
Several tool families overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded are near-identical routers (one is explicitly 'matches ask_pipeworx exactly'), deep_research overlaps the same router purpose, and five polymarket_* tools combine arbitrage, edges, spread, fill-risk, and tracker concerns. Detailed descriptions try to steer selection, but an agent can reasonably misselect between the ask_pipeworx variants and the discovery pair (discover_tools vs suggest_questions). Distinct clusters (memory, subscriptions, entity resolution) are clean, pulling the score to the middle.
All names use lowercase snake_case consistently, which is the key requirement. The pattern splits between verb_noun (predict_gender, compare_entities, resolve_entity, validate_claim, scan_dependency) and noun-first (entity_profile, recent_changes, polymarket_edges, ai_visibility_check), plus a namespaced family (ask_pipeworx_*, polymarket_*), a minor deviation but still readable and predictable.
33 tools is above the heavy threshold and includes clear redundancy (three ask_pipeworx variants, five polymarket tools) that inflates the surface. The breadth of data domains (SEC, FRED, FDA, patents, Polymarket, memory, subscriptions) does justify many of them, but the count is borderline-to-heavy for a coherent set.
Treated as a data-gateway, coverage is broad and coherent: research, entity resolution, comparison, change feeds, fact-checking, memory, subscriptions, and a full Polymarket analysis suite are present. Minor gaps exist (no generic record-fetch-by-URI tool despite search_within referencing gateway fetching, no account/key management), and the 'genderize' server name matches only 2 of 33 tools, signaling a domain labeling mismatch rather than a functional gap.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."entity_profile3 fields changedInput schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."Input schema / properties / type / enumPrevious value: -[
- "company"
-]New value: +[
+ "company",
+ "ticker"
+]Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."resolve_entity1 field changedInput schema / properties / value / descriptionPrevious value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."Nationalize MCP — nationality prediction from first name (nationalize.io, free, no auth)
Agify MCP — age prediction from first name (agify.io, free, no auth)
Harness the power of names with our Name Demographics MCP. Using Agify, Genderize, and Nationalize
Random User MCP — wraps randomuser.me (free, no auth)
Add one secure layer between your agents and this server.