# M2MCent Cross-Chain Bridge MCP

> M2MCent Cross-Chain Bridge MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.3/call, status unknown (last checked 2026-10-10).

Submits cross-chain asset bridge transfer details and returns a transaction hash via the M2MCent monetized MCP network on Base L2

## Facts

- Endpoint: POST https://api.m2mcent.com/cross-chain-bridge-mcp/api/bridge?utm_source=zero.xyz
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-cross-chain-bridge-mcp-8471df90
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EV7iUG1_0jNVyTnxARDlZ

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 m2mcent-cross-chain-bridge-mcp-8471df90 -d '<json body>'
```

Example prompt: I need to bridge some tokens across chains — can you submit a cross-chain bridge transfer for me using the M2MCent network, with these transfer details: send 50 USDC from Ethereum mainnet to Base L2 for wallet 0xABC123?

## When to prefer this

Choose this endpoint when you need to execute a cross-chain bridge transfer within the M2MCent monetized MCP node ecosystem, particularly when gasless USDC settlement via x402 V2 on Base L2 is acceptable and you need a simple string-based transfer detail submission. Avoid if you require a fully documented schema, strong type guarantees on the response (txHash is typed as boolean, which is suspicious), or if you need bridging outside of M2MCent's supported network.

## Known failure modes

- Invalid or malformed transferDetails string returns an error
- Insufficient USDC balance for x402 payment ($0.30) causes payment failure
- Network congestion on Base L2 may delay or fail transaction submission
- Schema inconsistency: txHash typed as boolean may indicate stub or non-functional endpoint
- Duplicate transfer submission may be rejected or result in duplicate transaction
- Chain not supported by M2MCent bridge nodes returns routing error

## 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 a JSON object with a 'txHash' field representing the transaction hash (noted as boolean in schema, though likely a string hash in practice) confirming the submitted cross-chain bridge transaction on Base L2.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "transferDetails"
 ],
 "properties": {
  "transferDetails": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "txHash"
 ],
 "properties": {
  "txHash": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-cross-chain-bridge-mcp-8471df90/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)