Ext Ops Panel
Open dashboard
Comparison

co.thinair/data vs U2 MCP Server

co.thinair/data is an MCP server published by thinair.co. Marketplaces we read that list it: 1 (Official MCP Registry). U2 MCP Server is an MCP server published by bpamiri. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
Marketplaceco.thinair/dataU2 MCP Server
Official MCP Registry Listed
Version: 2.2.2
No figure published
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 123
Downloads/week (PyPI): 32
Forks (GitHub): 1
Stars (GitHub): 6
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

co.thinair/data vs U2 MCP Server
Factco.thinair/dataU2 MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub6
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (data.thinair.co/mcp)On your machine (u2-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published10, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/bpamiri/u2-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno 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

co.thinair/data

In its own words, on Official MCP Registry:

PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.

U2 MCP Server

In its own words, on Official MCP Registry:

Connect AI assistants to Rocket Universe/UniData MultiValue databases via MCP.

How to run each

co.thinair/data As a remote MCP server

Claude Code
claude mcp add --transport http data https://data.thinair.co/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

U2 MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio u2-mcp -- uvx u2-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only co.thinair/data 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

The marketplaces of co.thinair/data publish no settings it asks for, so we do not compare settings.

What it can do: co.thinair/data · What it can do: U2 MCP Server · 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.

Where the data comes from: how the catalog is built