Bindingdb vs Biorxiv
A side-by-side look at the Bindingdb and Biorxiv MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bindingdb for biology & bioinformatics work as a local process; choose Biorxiv for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bindingdb when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Choose Biorxiv when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
details, biorxiv_details, published.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 41/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View Bindingdb | View Biorxiv |
Tools & capabilities
Bindingdb tools
No tool names declared yet. Check the project README from the listing page.
Biorxiv tools 7
detailsDEPRECATED ALIAS for biorxiv_details — identical behavior, kept for existing callers. New callers should use biorxiv_details.biorxiv_detailsbioRxiv / medRxiv preprint metadata by DOI or by date / date range.publishedDEPRECATED ALIAS for biorxiv_published — identical behavior, kept for existing callers. New callers should use biorxiv_published.biorxiv_publishedbioRxiv / medRxiv preprints that have since been published in a peer-reviewed journal.publisherDEPRECATED ALIAS for biorxiv_publisher — identical behavior, kept for existing callers. New callers should use biorxiv_publisher.biorxiv_publisherbioRxiv / medRxiv preprints subsequently published by a given DOI prefix (e.g. "10.1038" for Nature).summarybioRxiv submission/publication counts. Interval: "m" (monthly, default) or "y" (yearly). bioRxiv only — medRxiv has no /sum endpoint.
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.
Bindingdb
{
"mcpServers": {
"bindingdb": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-bindingdb"
]
}
}
}
Biorxiv
{
"mcpServers": {
"biorxiv": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-biorxiv"
]
}
}
}
Frequently asked questions
Bindingdb is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Biorxiv belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Bindingdb for biology & bioinformatics work and Biorxiv for biology & bioinformatics.
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.
Bindingdb has no declared pricing — check the project's own site. Biorxiv 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 bindingdb and biorxiv as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bindingdb has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Biorxiv has 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars.