# M2MCent AI Safety Metadata Indexer MCP Node #288

> M2MCent AI Safety Metadata Indexer MCP Node #288 is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $1.48462/call, status unknown (last checked 2026-10-10).

Executes a monetized MCP node endpoint claiming to index AI safety metadata, accessible via x402 micropayment on Base L2

## Facts

- Endpoint: POST https://api.m2mcent.com/ai-safety-metadata-indexer-mcp-288/api/execute?utm_source=zero.xyz
- Price: $1.48462/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-ai-safety-metadata-indexer-mcp-node-288-9f5914cc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FJ14ja3T87qFhTB8e_oHd

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-ai-safety-metadata-indexer-mcp-node-288-9f5914cc -d '<json body>'
```

Example prompt: Can you run the AI safety metadata indexer on M2MCent and pass these parameters to get back the result?

## When to prefer this

Only consider this endpoint if you specifically need to interact with M2MCent's AI safety metadata indexer node #288 and are prepared to pay ~$1.48 USDC per call via x402 on Base L2. The opaque input/output schema (a free-form string in, a boolean out) and very low crawl quality score suggest this endpoint may be auto-generated or poorly documented; prefer well-documented alternatives for AI safety metadata tasks.

## Known failure modes

- Payment failure: insufficient USDC balance for $1.48 per call fee
- Opaque response: hash field returns boolean rather than meaningful data, making it hard to interpret results
- Missing parameters: required 'parameters' string field not provided leads to schema validation error
- Subdomain routing failure: one of 205 subdomains may be unavailable
- Schema mismatch: response schema defines hash as boolean which is likely incorrect or placeholder documentation

## 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 containing a 'hash' field typed as boolean — the schema is minimal and largely opaque, providing little structured information about what was actually computed or retrieved.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-ai-safety-metadata-indexer-mcp-node-288-9f5914cc/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)