Touch Browser vs Openevidence MCP
A side-by-side look at the Touch Browser and Openevidence MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Touch Browser for research work as a local process; choose Openevidence MCP 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 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.
Choose Openevidence MCP when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 51/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 45 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Touch Browser | View Openevidence MCP |
Tools & capabilities
Touch Browser tools
No tool names declared yet. Check the project README from the listing page.
Openevidence MCP 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.
Touch Browser
{
"mcpServers": {
"nangman-infra-touch-browser": {
"command": "npx",
"args": [
"-y",
"@nangman-infra/touch-browser-mcp"
]
}
}
}
Openevidence MCP
{
"mcpServers": {
"openevidence-mcp": {
"command": "npx",
"args": [
"-y",
"openevidence-mcp"
]
}
}
}
Frequently asked questions
Touch Browser is categorized under Research and uses a local stdio subprocess. Openevidence MCP belongs to Research and uses a local stdio subprocess. Pick Touch Browser for research work and Openevidence MCP 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.
Touch Browser is listed as free. Auth: no auth required. Openevidence MCP 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 nangman-infra-touch-browser and openevidence-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Touch Browser has a quality signal of 51/100 (Good) with 3 views, 0 installs and 10 GitHub stars. Openevidence MCP has 48/100 (Fair) with 0 views, 0 installs and 45 GitHub stars.