Citeguard vs Touch Browser
A side-by-side look at the Citeguard and Touch Browser 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 Touch Browser for research as a local process. 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.
- You prefer a local stdio subprocess transport.
Choose Touch Browser when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 40/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
Citeguard tools
No tool names declared yet. Check the project README from the listing page.
Touch Browser 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
{
"mcpServers": {
"citeguard-3": {
"command": "uvx",
"args": [
"citationguard"
]
}
}
}
Touch Browser
{
"mcpServers": {
"nangman-infra-touch-browser": {
"command": "npx",
"args": [
"-y",
"@nangman-infra/touch-browser-mcp"
]
}
}
}
Frequently asked questions
Citeguard is categorized under Research and uses a local stdio subprocess. Touch Browser belongs to Research and uses a local stdio subprocess. Pick Citeguard for research work and Touch Browser 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. Touch Browser 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 nangman-infra-touch-browser 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. Touch Browser has 51/100 (Good) with 3 views, 0 installs and 10 GitHub stars.