# M2MCent Metaverse Legal Contract Validator MCP

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

Validates a metaverse legal contract by hash, returning a boolean URL/validity result via a monetized MCP node on the x402 protocol.

## Facts

- Endpoint: POST https://api.m2mcent.com/metaverse-legal-contract-validator-mcp-958/api/execute?utm_source=zero.xyz
- Price: $1.174831/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-metaverse-legal-contract-validator-mcp-99b13491
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Rzci2-8_AbcPbLPGzLu3X

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-legal-contract-validator-mcp-99b13491 -d '<json body>'
```

Example prompt: Can you validate this metaverse legal contract hash for me — the hash is 0xabc123def456 — and tell me if it passes the legal contract validator?

## When to prefer this

Choose this endpoint when you specifically need to validate a metaverse-context legal contract identified by a hash value and require a simple boolean pass/fail result via a pay-per-call x402 USDC micropayment model. Prefer alternatives if you need detailed validation reports, non-metaverse legal documents, or free-tier access.

## Known failure modes

- Missing or malformed 'hash' input field returns a validation error
- Hash not found in the index returns false or an error response
- Payment failure (x402 USDC settlement) results in a 402 response and the call is not executed
- Network or node unavailability returns a 5xx error
- Schema mismatch — the response 'url' field is typed as boolean despite the field name suggesting a URL, which may cause confusion in downstream parsing

## 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 'url' field (boolean) indicating whether the submitted contract hash passed legal validation. A true value signals valid; false signals invalid or not found.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-metaverse-legal-contract-validator-mcp-99b13491/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)