com.pitbridge/pitbridge vs MTContext
com.pitbridge/pitbridge is an MCP server published by pitbridge.com. Marketplaces we read that list it: 1 (Official MCP Registry). MTContext is an MCP server published by mtcontext. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  com.pitbridge/pitbridge |  MTContext |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2 Downloads/month (PyPI): 290 Downloads/week (PyPI): 76 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | com.pitbridge/pitbridge | MTContext |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (pitbridge) | Remote server (mcp.mtcontext.com/mcp/v1) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/toolstackvault/pitbridge | github.com/mtcontext/mtcontext-quickstart |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
com.pitbridge/pitbridge
Local-first MCP bridge for NinjaTrader 8 behind a deterministic guardrail engine.
MTContext
Connect any MCP client to MetaTrader 4/5 to read prices, manage positions, and place trades.
How to run each
com.pitbridge/pitbridge As a local MCP server: PyPI package
claude mcp add --transport stdio pitbridge -- uvx pitbridge mcpMTContext As a remote MCP server
claude mcp add --transport http mtcontext https://mcp.mtcontext.com/mcp/v1 --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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: com.pitbridge/pitbridge · What it can do: MTContext · 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.