QueryBear vs io.github.txn2/mcp-trino
QueryBear is an MCP server published by spencerpauly. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.txn2/mcp-trino is an MCP server published by txn2. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  QueryBear |  io.github.txn2/mcp-trino |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 1 Stars (GitHub): 5 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 | QueryBear | io.github.txn2/mcp-trino |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 5 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.querybear.com/mcp) | On your machine (https://github.com/txn2/mcp-trino/releases/download/v0.2.1/mcp-trino_0.2.1_darwin_arm64.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/txn2/mcp-trino |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | 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
QueryBear
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
io.github.txn2/mcp-trino
MCP server for Trino data warehouses. Query, analyze plans, and explore schemas.
How to run each
QueryBear As a remote MCP server
claude mcp add --transport http querybear https://mcp.querybear.com/mcpio.github.txn2/mcp-trino
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only QueryBear has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: QueryBear · What it can do: io.github.txn2/mcp-trino · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.