# M2MCent DeFi Malware Monitor MCP Node

> M2MCent DeFi Malware Monitor MCP Node is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.918966/call, status unknown (last checked 2026-10-09).

Executes a DeFi malware monitoring query via a monetized remote MCP node, returning a boolean status result for the submitted payload.

## Facts

- Endpoint: POST https://api.m2mcent.com/defi-malware-monitor-mcp-331/api/execute?utm_source=zero.xyz
- Price: $0.918966/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-09
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/m2mcent-defi-malware-monitor-mcp-node-1a4c95f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R4_ewI1gk0J6zb3y8LXtU

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-defi-malware-monitor-mcp-node-1a4c95f2 -d '<json body>'
```

Example prompt: Can you run a DeFi malware check on this smart contract address — 0xAbCd1234... — and tell me if it's flagged as malicious?

## When to prefer this

Choose this endpoint when you need a quick boolean malware/threat check on a DeFi contract, wallet, or transaction payload and are operating within the x402 micropayment ecosystem on Base L2. It is best suited for lightweight, real-time safety gates in DeFi workflows where a simple pass/fail signal is sufficient. Avoid if you need detailed malware reports, human-readable explanations, or structured threat intelligence — the response schema only returns a status boolean.

## Known failure modes

- Missing or empty payload returns validation error
- Malformed payload string causes processing failure
- Unrecognized contract address or transaction hash returns indeterminate status
- Network or node timeout results in no response
- Payment failure via x402 protocol blocks execution
- Boolean-only response provides no diagnostic detail on why something was flagged

## 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 'status' field indicating whether the malware monitoring check passed or detected an issue. A true value likely indicates a clean/safe result; false indicates a flagged or malicious finding. No detailed breakdown or explanation is included in the minimal schema.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/m2mcent-defi-malware-monitor-mcp-node-1a4c95f2/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)