A side-by-side look at the Citeguard and GeniusFlow Federation MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Citeguard for research work as a local process; choose GeniusFlow Federation for research over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Citeguard when
You need dedicated capabilities in the Research domain.
No tool names declared yet. Check the project README from the listing page.
GeniusFlow Federation 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.
Citeguard is categorized under Research and uses a local stdio subprocess. GeniusFlow Federation belongs to Research and uses a remote HTTP/SSE transport. Pick Citeguard for research work and GeniusFlow Federation for research.
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.
Citeguard has no declared pricing — check the project's own site. GeniusFlow Federation is listed as free. Auth: no auth required. 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 citeguard-3 and geniusflow-federation as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Citeguard has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. GeniusFlow Federation has 40/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.