Jekakos MCP User Data Enrichment vs Tinder Bio
A side-by-side look at the Jekakos MCP User Data Enrichment and Tinder Bio MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jekakos MCP User Data Enrichment for social media work; choose Tinder Bio for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Jekakos MCP User Data Enrichment when
- You need dedicated capabilities in the Social Media domain.
Choose Tinder Bio when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tinder_bio_generate.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 28/100 · Emerging | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Jekakos MCP User Data Enrichment | View Tinder Bio |
Tools & capabilities
Jekakos MCP User Data Enrichment tools
No tool names declared yet. Check the project README from the listing page.
Tinder Bio tools 1
tinder_bio_generateGenerate a dating profile bio. Red flags embedded at no extra charge.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Jekakos MCP User Data Enrichment
No confirmed install command for Jekakos MCP User Data Enrichment yet — follow the setup steps linked from its listing page rather than a guessed package name.
Tinder Bio
{
"mcpServers": {
"tinder-bio": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tinder-bio"
]
}
}
}