# M2MCent Supply Chain Metadata Monitor MCP

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

Executes a query against the supply-chain-metadata-monitor MCP node, returning a boolean result via the M2MCent monetized MCP network.

## Facts

- Endpoint: POST https://api.m2mcent.com/supply-chain-metadata-monitor-mcp-469/api/execute?utm_source=zero.xyz
- Price: $0.597399/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-supply-chain-metadata-monitor-mcp-4b88a010
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6sPpKLsaKhNtT3vupXQSm

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-supply-chain-metadata-monitor-mcp-4b88a010 -d '<json body>'
```

Example prompt: Check whether our supplier shipment metadata is flagged or clean — run the query 'is_shipment_delayed:vendor_42' through the M2MCent supply chain metadata monitor and tell me if it comes back true or false.

## When to prefer this

Use this endpoint when you need a lightweight boolean check against supply chain metadata state and want to avoid heavy context usage — the MCP node returns a simple true/false, making it ideal for conditional workflow branching. Prefer this over full data retrieval endpoints when you only need to verify a condition rather than fetch full records.

## Known failure modes

- Query string is empty or malformed — API may return an error or unexpected boolean
- Payment settlement failure via x402 protocol — request may be rejected before execution
- MCP node unavailable or unresponsive — connection timeout or 5xx error
- Ambiguous query not matched to known metadata keys — may return false as default
- Rate limiting or quota exceeded on the monetized node

## 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

A JSON object containing a single 'result' field with a boolean value (true or false) indicating whether the queried supply chain metadata condition holds.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-supply-chain-metadata-monitor-mcp-4b88a010/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)