Verified Handles vs Xflux
A side-by-side look at the Verified Handles and Xflux MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
Verified HandlesSocial MediaLook up people, organisations and things, and their verified social handles and identifiers.55GoodAuth: not declaredVerdict: choose Verified Handles for social media work; choose Xflux 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?
VChoose Verified Handles when
- You need dedicated capabilities in the Social Media domain.
- You want tools like
get_entry, search_entries, find_by_handle.
Choose Xflux when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
XFLUX_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Verified Handles | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 55/100 · Good | 43/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | XFLUX_API_KEY |
| Verified owner |
Tools & capabilities
Verified Handles tools 5
get_entryOne entry, by VHID, short name or Wikidata QID: its public record (title, description, handles, image, URL) and, as `editing`, what the editor would load for this key — the current revision, the editable fields, every handle with who manages it (the Wikidata sync or the site), which fields the sync manages, and whether this key may edit it live. Without an API key, the public record alone.search_entriesSearch the entries as the site search does: words match titles, subtitles and descriptions; a Wikidata QID finds the entries linked to it; a VHID finds that entry and the entries that link to it.find_by_handleWhich public entries list a handle: “is x.com/someone an official account, and whose?”. Give a profile’s address as url (https://x.com/someone), or platform (its catalog id: twitter, instagram, youtube, …) and value (someone or @someone). Answers each entry’s VHID, title and URL, the handle as the entry lists it, and whether that handle is verified; an empty list when no entry lists it. Case is ignored where the platform ignores it. Email addresses are not looked up.get_entry_historyAn entry’s public edit history, newest first (`next_offset` pages on). A merged entry’s key gives its own history.get_entriesUp to 50 entries’ public records in one call, by VHID or short name (not a Wikidata QID: get_entry or search_entries finds an entry by its item), each answered as get_entry answers it signed out — the entry, or not_found — in the order given. A name given twice is answered once.
Xflux tools
No tool names declared yet. Check the project README from the listing page.
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.
Verified Handles
No confirmed install command for Verified Handles yet — follow the setup steps linked from its listing page rather than a guessed package name.
Xflux
{
"mcpServers": {
"xflux": {
"command": "npx",
"args": [
"-y",
"@xflux/xflux-mcp-server"
],
"env": {
"XFLUX_API_KEY": "YOUR_XFLUX_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Verified Handles is categorized under Social Media and uses an install path we have not confirmed yet. Xflux belongs to Social Media and uses a local stdio subprocess. Pick Verified Handles for social media work and Xflux for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Verified Handles has no confirmed install command yet — follow its own setup instructions.
Verified Handles is listed as free. Xflux has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add verified-handles and xflux as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Verified Handles has a quality signal of 55/100 (Good) with 0 views, 0 installs and 31 GitHub stars. Xflux has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.