# mq-bridge-app (oci · ghcr.io/marcomq/mq-bridge-app:0.4.15)

Move data between 15+ databases, queues and files at high throughput, without it entering context

- Trust score: 36/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- oci · `ghcr.io/marcomq/mq-bridge-app:0.4.15`: 36/100 (this document), [markdown](https://verifymcp.io/servers/marcomq-mq-bridge-app/ghcr-io-marcomq-mq-bridge-app-0-4-15.md), [page](https://verifymcp.io/servers/marcomq-mq-bridge-app/ghcr-io-marcomq-mq-bridge-app-0-4-15)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/marcomq/mq-bridge-app:0.4.15`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2334 tokens (~212/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agent_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: 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.

## Install

### 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:0.4.15. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add marcomq-mq-bridge-app -- docker run --rm -i ghcr.io/marcomq/mq-bridge-app:0.4.15
```

### Cursor

```json
{
  "mcpServers": {
    "marcomq-mq-bridge-app": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/marcomq/mq-bridge-app:0.4.15"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "marcomq-mq-bridge-app": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/marcomq/mq-bridge-app:0.4.15"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add marcomq-mq-bridge-app -- docker run --rm -i ghcr.io/marcomq/mq-bridge-app:0.4.15
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marcomq-mq-bridge-app": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/marcomq/mq-bridge-app:0.4.15"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  marcomq-mq-bridge-app:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/marcomq/mq-bridge-app:0.4.15"]
```

### Netclaw

```json
{
  "McpServers": {
    "marcomq-mq-bridge-app": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/marcomq/mq-bridge-app:0.4.15"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "marcomq-mq-bridge-app": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/marcomq/mq-bridge-app:0.4.15"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 36)

First indexed and scored.

## MCP tools (11)

### `agent_listen` (~309 tokens)

Open this server's agent inbox so other agents on this machine can send it messages, and tail it for the rest of the session. Only exists when the server was started with `--agent-bus`, and off until called — nothing can reach this agent before that. `name` is what peers address it by. Messages are then collected with `route_messages` on route `agent-inbox`; reads are destructive, and only the last `capture_last` (default 200) are held — the durable inbox is drained into that buffer, so mail beyond it is discarded, not queued. By default the inbox is a local directory under `$MQB_AGENTS_DIR` (default `~/.mqb-agents`), which any process able to write a file can post to; pass `input` to receive over a broker instead. Calling it twice is an error — one inbox per server.

Input parameters:

- `capture_last` (integer|null): How many messages to hold for `route_messages`. Defaults to 200.
- `input`: Optional source endpoint replacing the default local directory — any connector, e.g. `{"nats": {"url": "...", "stream": "AGENTS", "subject": "agents.me"}}`, to receive from agents that are not on thi…
- `name` (string, required): The name other agents address this one by. Becomes a directory under `$MQB_AGENTS_DIR` (default `~/.mqb-agents`).

### `agent_send` (~214 tokens)

Send a message to another agent's inbox on this machine. Always available: sending needs no opt-in, because it only writes into a mailbox the recipient chose to open with `agent_listen`. `to` is the peer's name — `server_info` lists the peers that have an inbox and which are currently listening. Delivery is a single atomically written file, so a peer that is not running collects the message when it next listens. Pass `output` instead of `to` to reach an agent over a broker rather than this filesystem. A sender that has not called `agent_listen` is delivered as `from: "unnamed"` and cannot be replied to.

Input parameters:

- `message` (required): The message to deliver — a string, or any JSON value.
- `output`: Optional sink endpoint replacing the recipient's local inbox directory, for an agent reachable over a broker rather than this filesystem.
- `to` (string|null): The recipient agent's name. Required unless `output` names the target explicitly.

### `generate_cli_command` (~149 tokens)

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.

Input parameters:

- `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` (required): The same route JSON accepted by `start_route`.

### `list_routes` (~35 tokens)

List the routes started by this server, with their live connection health, total messages moved, current message rate, and achieved average rate.

### `publish` (~223 tokens)

Publish one message or a batch of messages to any endpoint. The target is supplied inline as endpoint 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).

Input parameters:

- `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` (required): Target endpoint, keyed by connector type, e.g. `{"kafka": {"url": "localhost:9092", "topic": "orders"}}` or `{"file": {"path": "/tmp/out.jsonl"}}`.

### `route_messages` (~64 tokens)

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.

Input parameters:

- `name` (string, required): The route name.

### `route_status` (~109 tokens)

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.

Input parameters:

- `name` (string|null): A specific route name; omit to report every running route.

### `server_info` (~73 tokens)

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.

### `start_route` (~602 tokens)

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). Returns the route name for use with wait_route / route_status / stop_route, plus the tuning that took effect.

Input parameters:

- `batch_size` (integer|null): Batch size. Overrides `batch_size` inside `route` if both are given; if neither is given the app default (1024) applies, not the library's 512.
- `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` (required): 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": {"…

### `stop_route` (~49 tokens)

Stop a running route by `name`. Returns the total messages it moved plus the rate it achieved (`average_messages_per_second` over `elapsed_s`).

Input parameters:

- `name` (string, required): The route name.

### `wait_route` (~179 tokens)

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.

Input parameters:

- `name` (string, required): 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.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/marcomq-mq-bridge-app/ghcr-io-marcomq-mq-bridge-app-0-4-15#diagnostics

## Score history

- 2026-09-25: 36

## Common questions

### 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:0.4.15).

### Is the mq-bridge-app MCP server safe to use?

mq-bridge-app scores 36 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: agent_listen, agent_send, generate_cli_command, list_routes, publish, and 6 more. Their descriptions and schemas cost roughly 2,006 tokens of context every time the server is loaded.

### Is the mq-bridge-app MCP server still maintained?

mq-bridge-app is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Repository: https://github.com/marcomq/mq-bridge
- Website: https://marcomq.github.io/mq-bridge/MCP.html
- Changelog RSS feed: https://verifymcp.io/servers/marcomq-mq-bridge-app/ghcr-io-marcomq-mq-bridge-app-0-4-15.xml
- Changelog JSON feed: https://verifymcp.io/servers/marcomq-mq-bridge-app/ghcr-io-marcomq-mq-bridge-app-0-4-15.json
- HTML version of this page: https://verifymcp.io/servers/marcomq-mq-bridge-app/ghcr-io-marcomq-mq-bridge-app-0-4-15