Back to Browse
Mixer Deposit Detector MCP
x402
Mixer Deposit Detector MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.3/call, status unknown (last checked 2026-09-15).
Detects cryptocurrency mixer deposits by analyzing transaction data for patterns associated with mixing services
Price / call$0.3
Success—
StatusUnknown
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 detection result indicating whether the provided transaction data shows signs of cryptocurrency mixer involvement, including pattern indicators and likely a risk classification or confidence score for mixing activity.
Example use cases
AML compliance screening for incoming deposits
“I just received a crypto deposit and need to verify it didn't come through a mixer like Tornado Cash — can you run this transaction data through the mixer deposit detector and flag it if it's suspicious?”
Exchange onboarding risk check
“Before we approve this new user's first deposit, can you analyze their transaction data to detect any mixer involvement so we can decide whether to proceed with onboarding?”
DeFi protocol treasury audit
“We need to screen these incoming transactions to our treasury wallet for any mixer deposits — run each one through the mixer deposit detector and tell me which ones show tumbling or mixing patterns.”
Technical details
Endpoint
POSThttps://api.m2mcent.com/mixer-deposit-detector-mcp/api/processWhen to prefer
Choose this endpoint when you need automated, per-transaction screening of cryptocurrency data for mixer or tumbling service involvement, particularly in AML/compliance workflows where flagging obfuscated fund origins is critical. Prefer this over generic blockchain explorers when you specifically need mixer pattern detection rather than raw transaction lookup.
Side effects
- Malformed or missing 'data' field in request body returns validation error
- Unrecognized transaction format may yield inconclusive detection result
- Network timeout or service unavailability returns HTTP 5xx error
- Insufficient transaction data may result in low-confidence or null result
- Payment failure (x402) prevents endpoint access
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| payload | string |
Output
Schema · Response
{
"type": "json",
"example": {
"success": true
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"