Bindingdb vs NeoSQL MCP
Bindingdb is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). NeoSQL MCP is an MCP server published by unvus. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Bindingdb |  NeoSQL MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.8.11 Downloads/month (npm): 2 661 Downloads/week (npm): 291 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.8.11 Downloads/month (npm): 2 661 Downloads/week (npm): 291 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Bindingdb | NeoSQL MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | Remote server (gateway.pipeworx.io/bindingdb/mcp) | On your machine (neosql-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/pipeworx-io/mcp-bindingdb | github.com/unvus/neosql-mcp |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Bindingdb
BindingDB — measured protein/small-molecule binding affinities.
NeoSQL MCP
Schemas, SQL, ERDs, and codegen for PostgreSQL, MySQL, Oracle, SQLite, and more via NeoSQL Desktop.
How to run each
Bindingdb As a remote MCP server
claude mcp add --transport http bindingdb https://gateway.pipeworx.io/bindingdb/mcpNeoSQL MCP As a local MCP server: npm package
claude mcp add --transport stdio neosql-mcp -- npx -y neosql-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Bindingdb has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of NeoSQL MCP nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Bindingdb · What it can do: NeoSQL MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.