# M2MCent Fintech Metadata Auditor MCP Node

> M2MCent Fintech Metadata Auditor MCP Node is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $1.099525/call, status unknown (last checked 2026-10-12).

Executes a fintech metadata audit operation on a monetized MCP node, returning a URL result given a hash input, settled via x402 USDC micropayment on Base L2.

## Facts

- Endpoint: POST https://api.m2mcent.com/fintech-metadata-auditor-mcp-213/api/execute?utm_source=zero.xyz
- Price: $1.099525/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-fintech-metadata-auditor-mcp-node-d7745834
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YjVY5g_3i5JzYilf_fOUH

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-fintech-metadata-auditor-mcp-node-d7745834 -d '<json body>'
```

Example prompt: Run a fintech metadata audit on hash 'abc123def456' using the M2MCent auditor node — I need to know if the result resolves correctly.

## When to prefer this

Choose this endpoint when you specifically need to execute a fintech metadata audit on a hash value via a monetized MCP node that settles payments gaslessly in USDC on Base L2 via x402. Be cautious: the response schema is poorly defined (url field typed as boolean), there are many identical sibling endpoints suggesting auto-generation, and the crawl quality score is low.

## Known failure modes

- Missing or invalid 'hash' field returns a 400-level error
- Payment failure via x402 protocol results in 402 response blocking execution
- Hash not found or unrecognized returns an unexpected or null result
- Schema mismatch — 'url' field typed as boolean may indicate unstable or auto-generated API
- High volume of identical sibling endpoints suggests auto-generated stubs with unreliable behavior

## 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 (typed as boolean in the schema) indicating the outcome of the fintech metadata audit for the submitted hash. The schema is minimal and the actual semantic meaning of the boolean url field is unclear from available metadata.

## 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-fintech-metadata-auditor-mcp-node-d7745834/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)