# M2MCent IoT Malware Indexer MCP

> M2MCent IoT Malware Indexer MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $1.344971/call, status unknown (last checked 2026-10-13).

Indexes or checks IoT malware data, returning a boolean report on the submitted data string

## Facts

- Endpoint: POST https://api.m2mcent.com/iot-malware-indexer-mcp-339/api/execute?utm_source=zero.xyz
- Price: $1.344971/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-iot-malware-indexer-mcp-123fd1ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IdlITKoDZ_PsufZ4BrKx6

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-iot-malware-indexer-mcp-123fd1ab -d '<json body>'
```

Example prompt: Can you run this IoT device payload through the malware indexer and tell me if it flags as malicious: 'device_id=abc123&fw=1.2.3&beacon=0xDEADBEEF'?

## When to prefer this

Use this endpoint when you need a fast, low-cost boolean malware check against an IoT-focused malware index and can submit the suspect data as a string. Prefer it over general-purpose threat feeds when your use case is specifically IoT device data, firmware strings, or device identifiers, and you want a simple pass/fail result rather than a detailed threat report.

## Known failure modes

- Missing or empty 'data' field returns a validation error
- Non-string data type in 'data' field causes schema rejection
- Payment failure via x402 protocol results in 402 response and no execution
- Ambiguous or extremely short data strings may yield unreliable boolean results
- Service unavailability returns 5xx with no report

## 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 single boolean field 'report' — true if the submitted data matches a malware index entry, false if it does not.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-iot-malware-indexer-mcp-123fd1ab/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)