mq-bridge-app
OCI · GHCR.IO/MARCOMQ/MQ-BRIDGE-APP
Move data between 15+ databases, queues and files at high throughput, without it entering context
Available components
Last scanned (13 hours ago)
Scores higher than 71% of OCI servers
Category Data and Analytics
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Renamed to io.github.marcomq/mq-bridge.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 31 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2139 tokens (~194/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Nov 26 0
- Package version: 1.0.0 → 1.0.2 functional
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- 12 Nov 26 0
- Package version: 1.0.0 → 1.0.2 functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
- Stability: fail → 0.87 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 75 to 78.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 68 to 72.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 62 to 65.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed oci/ghcr.io/marcomq/mq-bridge-app@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bridge_status ~131
Report every mq-bridge process this user is running on this machine — CLI jobs (`mqb copy`, headless configs), other MCP servers, the web UI and the desktop app — with their routes and consumers: connector types, running/healthy, `outcome`, current rate (`throughput`), `average_throughput`, total messages (`message_sequence`), `pending` and `started_at_ms`. Read-only; routes of other processes cannot be stopped from here. The entry whose `pid` equals `current_pid` is this server. Error text of other processes is redacted to `error`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
describe ~128
Describe the endpoints and middlewares this build supports, the same data as `mqb list --json` / `mqb describe <name> --json`: each endpoint's `endpoint` type (the JSON key `publish`/`start_route` take), URI form, example and typed `params` (also its config fields), and each middleware's params. Pass `name` to narrow it to one entry.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string|null | – | A scheme (`kafka`), alias, endpoint type (`sqlx`) or middleware (`retry`). Omit it for the whole catalog. |
No output schema declared.
No examples provided.
generate_cli_command ~149
Generate a copyable, headless `mqb` command for a route. Accepts the same route JSON and tuning overrides as `start_route`, but does not start anything. The command embeds canonical JSON with POSIX shell quoting so fields that have no compact copy-URI representation are preserved. Credential values are replaced by environment variable placeholders and the required variable names are returned separately.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_size | integer|null | – | Batch size. Overrides a value inside `route`. |
| concurrency | integer|null | – | Route concurrency. Overrides a value inside `route`. |
| name | string|null | – | Optional route name in the generated configuration. |
| route | – | yes | The same route JSON accepted by `start_route`. |
No output schema declared.
No examples provided.
list_routes ~35
List the routes started by this server, with their live connection health, total messages moved, current message rate, and achieved average rate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish ~226
Publish one message or a batch of messages to any endpoint. The endpoint is supplied inline in `publisher` as JSON keyed by type (e.g. {"kafka": {"url": "...", "topic": "..."}}); this is independent of routes. Provide either `message` or `messages`; each message has a `payload` and optional `metadata` headers (e.g. `kind` for the message type, `correlation_id`). Returns the send outcome (an acknowledgement, or the endpoint's reply for request/reply endpoints).
| Name | Type | Req | Description |
|---|---|---|---|
| message | – | – | A single message to send. |
| messages | array|null | – | A batch of messages to send (alternative to `message`). |
| name | string|null | – | Optional label for this target, used to group sends in status reporting. Defaults to the connector type. |
| publisher | – | yes | Target endpoint, keyed by connector type, e.g. `{"kafka": {"url": "localhost:9092", "topic": "orders"}}` or `{"file": {"path": "/tmp/out.jsonl"}}`. |
No output schema declared.
No examples provided.
route_messages ~64
Return the most recent messages captured on a route, newest last. Only routes started with `capture_last` capture anything. Reads are destructive: each message is returned once, so repeated calls yield only what arrived since the last call.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The route name. |
No output schema declared.
No examples provided.
route_status ~109
Report the live status of one route (by `name`) or all routes: connection health, whether it has finished, the total number of messages it has moved, its current rate (`messages_per_second`), and the rate it achieved overall (`average_messages_per_second` over `elapsed_s`). Quote the average for a finished job: the current rate decays to ~0 once a route stops moving data.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string|null | – | A specific route name; omit to report every running route. |
No output schema declared.
No examples provided.
server_info ~73
Report this MCP server's build identity: crate `version`, `git_hash` (with a `-dirty` suffix if the working tree had uncommitted changes at build time), build `profile` (debug/release), and `build_time`. Use it to confirm which binary is actually running before trusting throughput numbers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_route ~628
Create and run a route that moves messages from its `input` (source) endpoint to its `output` (sink) endpoint, each keyed by connector type. Supports route options like `concurrency`, `batch_size`, and `exit_on_empty` (drain the source then exit; otherwise the route runs continuously until stopped). Either endpoint may carry a `middlewares` array — `retry`, `dlq`, `deduplication`, `limiter`, `transform`, `compression`, `encryption`, `pack`/`unpack`, `buffer`, `delay`, `timeout`, `weak_join`, `cookie_jar`, `metrics` — e.g. `{"sqlx": {...}, "middlewares": [{"retry": {"max_attempts": 3}}]}`. `concurrency`/`batch_size` may be given inside `route` or as top-level arguments — the top-level argument wins, and an unset value becomes the app default (4 / 1024, or the batch size the output endpoint's schema declares). Returns the route name for use with wait_route / route_status / stop_route, plus the tuning that took effect.
| Name | Type | Req | Description |
|---|---|---|---|
| batch_size | integer|null | – | Batch size. Overrides `batch_size` inside `route` if both are given; if neither is given, the output endpoint's own schema default applies if it declares one, else the app default (1024), not the lib… |
| capture_last | integer|null | – | Keep the last N messages that flow through this route, readable with `route_messages`. Omit (or 0) to capture nothing, which is the default — captured payloads are held in memory and returned to the… |
| concurrency | integer|null | – | Route concurrency. Overrides `concurrency` inside `route` if both are given; if neither is given the app default (4) applies, not the library's 1. Higher values parallelize sink writes; sources that… |
| name | string|null | – | Optional unique route name (auto-generated if omitted). |
| route | – | yes | The route to run: an `input` (source) endpoint and an `output` (sink) endpoint — each keyed by connector type, e.g. `{"input": {"nats": {"url": "localhost:4222", "subject": "orders"}}, "output": {"… |
No output schema declared.
No examples provided.
stop_route ~49
Stop a running route by `name`. Returns the total messages it moved plus the rate it achieved (`average_messages_per_second` over `elapsed_s`).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The route name. |
No output schema declared.
No examples provided.
wait_route ~179
Block until a route finishes, then report how it ended. Use this instead of polling `route_status` for a job started with `exit_on_empty`: it costs one tool call regardless of how long the job runs. Returns `finished` (false if `timeout_ms` elapsed first — the route is left running), the `outcome`, the total messages moved and the rate achieved. An `outcome` of `failed` carries the cause in `error`. Default timeout 60000 ms, maximum 18000000 ms.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The route name. |
| timeout_ms | integer|null | – | How long to wait before giving up and returning `finished: false`, in milliseconds. Defaults to 60000; values above 18000000 are clamped. The route keeps running when the wait times out. |
No output schema declared.
No examples provided.
How do I install the mq-bridge-app MCP server?
mq-bridge-app runs locally as a container image, launched with docker run --rm -i ghcr.io/marcomq/mq-bridge-app:1.0.2 mcp --transport stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/marcomq/mq-bridge-app
claude mcp add marcomq-mq-bridge-app -- docker run --rm -i ghcr.io/marcomq/mq-bridge-app:1.0.2 mcp --transport stdio
What is the mq-bridge-app MCP server?
mq-bridge-app is an MCP server listed in the public MCP registry as io.github.marcomq/mq-bridge-app. Move data between 15+ databases, queues and files at high throughput, without it entering context. This page covers its container image (ghcr.io/marcomq/mq-bridge-app).
Is the mq-bridge-app MCP server safe to use?
mq-bridge-app scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the mq-bridge-app MCP server expose?
mq-bridge-app exposes 11 tools: bridge_status, describe, generate_cli_command, list_routes, publish, and 6 more. Their descriptions and schemas cost roughly 1,771 tokens of context every time the server is loaded.
Is the mq-bridge-app MCP server still maintained?
mq-bridge-app is marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the mq-bridge-app MCP server?
VerifyMCP ran 12 checks on mq-bridge-app, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about mq-bridge-app: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.