bingx-ai-skills vs FreightUtils MCP Server
bingx-ai-skills is a plugin bundle for AI coding tools published by BingX. Marketplaces we read that list it: 1 (Community GitHub marketplaces). FreightUtils MCP Server is an MCP server published by SoapyRED. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. 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 |   FreightUtils MCP Server | |
|---|---|---|
| Community marketplace bingx-api/api-ai-skills | Listed Version: 0.1.3 Forks (GitHub): 6 Stars (GitHub): 20 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.22.5 Downloads/month (npm): 2 131 Downloads/week (npm): 1 439 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.22.5 Downloads/month (npm): 2 131 Downloads/week (npm): 1 439 Forks (GitHub): 0 Stars (GitHub): 7 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 | bingx-ai-skills | FreightUtils MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 20 (better) | 7 (worse) |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 29 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bingx-api/api-ai-skills | github.com/soapyred/freightutils-mcp |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 33 h ago |
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
bingx-ai-skills
29 BingX trading skills — USDT-M perpetual (market/trade/account), Spot (market/trade/account/wallet), Coin-M perpetual, Copy trading, Account management, Technical analysis, RSI bottom hunter, Maker entry, Trade review, Dynamic SL/TP, Sentiment dashboard, Trading plan
FreightUtils MCP Server
Neutral freight reference + validation layer for AI agents: ADR, HS, UN/LOCODE, freight math
How to run each
bingx-ai-skills As a Claude Code plugin
/plugin marketplace add bingx-api/api-ai-skills
/plugin install bingx-ai-skills@bingx-ai-skillsFreightUtils MCP Server As a remote MCP server
claude mcp add --transport http freightutils https://www.freightutils.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only FreightUtils MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of bingx-ai-skills 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: bingx-ai-skills · What it can do: FreightUtils MCP Server · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.