# M2MCent Metaverse Smart Contract Indexer MCP Node

> M2MCent Metaverse Smart Contract Indexer MCP Node is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.100921/call, status unknown (last checked 2026-10-11).

Executes a metaverse smart contract indexing query via a monetized remote MCP node, returning a boolean prediction result.

## Facts

- Endpoint: POST https://api.m2mcent.com/metaverse-smart-contract-indexer-mcp-705/api/execute?utm_source=zero.xyz
- Price: $0.100921/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-metaverse-smart-contract-indexer-mcp-node-03f0e412
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0DC2sEka41JGNAxwaSNE8

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-metaverse-smart-contract-indexer-mcp-node-03f0e412 -d '<json body>'
```

Example prompt: Can you query the metaverse smart contract indexer to check whether contract 0xABC123 on Base L2 satisfies the indexing condition I described?

## When to prefer this

Choose this endpoint when you need a simple true/false answer from a metaverse smart contract index query over the x402 payment protocol on Base L2, and you want gasless USDC micropayment settlement without managing gas fees directly. Best suited for lightweight boolean contract state checks rather than rich structured data retrieval.

## Known failure modes

- Missing or malformed 'parameters' string returns a 400 validation error
- x402 payment failure (insufficient USDC balance) returns a 402 Payment Required response
- Unrecognized contract address or parameters may return a false prediction rather than an error
- Network latency on Base L2 may cause timeouts
- Vague or improperly formatted parameter string may yield incorrect boolean results

## 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 'prediction' field with a boolean value (true/false), indicating whether the queried smart contract condition or indexing check evaluates as true or false.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-metaverse-smart-contract-indexer-mcp-node-03f0e412/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)