# MQTT v5 Broker Bridge MCP

> MQTT v5 Broker Bridge MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.12/call, status unknown (last checked 2026-09-15).

Bridges MQTT v5 broker messages and protocol commands via an agentic MCP-compatible API endpoint

## Facts

- Endpoint: POST https://api.m2mcent.com/mqtt-v5-broker-bridge-mcp/api/process
- Price: $0.12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mqtt-v5-broker-bridge-mcp-cbb25b44
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3jsL1BcJ7Ge0D2iPmcj17

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability mqtt-v5-broker-bridge-mcp-cbb25b44 -d '<json body>'
```

Example prompt: Bridge this sensor telemetry payload to my MQTT v5 broker — forward the message data so it gets routed through the broker bridge and delivered to the target topic.

## When to prefer this

Choose this endpoint when you need to programmatically bridge or relay MQTT v5 messages between brokers within an agentic or automated workflow, especially when integrating IoT telemetry pipelines that require a pay-per-call, API-accessible MQTT bridge without managing broker infrastructure directly.

## Known failure modes

- Malformed or missing data string returns a 400 validation error
- Broker bridge connection timeout if the downstream MQTT broker is unreachable
- Payment failure or insufficient USDC balance blocks the request via x402
- Invalid MQTT v5 message structure causes broker rejection
- Network latency or broker unavailability results in relay failure

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns the broker bridge response confirming message relay, routing status, or protocol acknowledgement from the MQTT v5 broker bridge after processing the submitted data payload.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payload": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mqtt-v5-broker-bridge-mcp-cbb25b44/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)