AurelianFlo
Pay-per-call MCP tools anchored around OFAC wallet screening, crypto wallet sanctions checks, OFAC exposure forecasts, review queue optimization, EDD memos, and document output. Start with server_capabilities and use the direct origin for paid execution.
MCP Endpoint
https://api.aurelianflo.com/mcp
Server Card
https://api.aurelianflo.com/.well-known/mcp/server-card.json
Privacy
https://api.aurelianflo.com/mcp/privacy
Support
https://api.aurelianflo.com/mcp/support
Tools
- server_capabilities: Free connection and capability check for the direct MCP endpoint and x402 payment requirements.
- queue_saved_list: Free status check explaining that review queues should be saved by the client or recreated from their original inputs.
- report_saved_retrieve: Free status check explaining that generated reports are returned inline and must be retained by the client.
- compliance_edd_report: Enhanced due diligence memo with status labels, evidence summary, required follow-up, and json, pdf, or docx output.
- compliance_exposure_forecast: OFAC exposure forecast with history basis, current exact-match baseline, per-wallet risk, and model limitations.
- compliance_queue_optimize: Review queue optimizer that pins current OFAC matches first and ranks the remainder by forecast risk and metadata.
- wallet_ofac_batch: Batch OFAC wallet screening with structured JSON output for a whole wallet set.
- wallet_ofac_report: One-call OFAC wallet screening with json, pdf, or docx output.
- wallet_ofac_screen: Exact-match OFAC wallet screening with the structured report payload returned in JSON.
- report_pdf_generate: Generate a PDF from a structured report payload.
- report_docx_generate: Generate a DOCX document from a structured report payload.
Bundles
- Compliance bundle: compliance_edd_report turns a wallet set plus case metadata into a reviewable memo with json, pdf, or docx output, while compliance_exposure_forecast and compliance_queue_optimize support triage before memo generation.
- Building blocks: compliance_edd_report, compliance_exposure_forecast, compliance_queue_optimize, or wallet_ofac_batch plus report_pdf_generate or report_docx_generate remains available for compliance clients that want to control the artifact step.
Proof
- Compliance canary: compliance_edd_report screened a two-wallet counterparty set, flagged Lazarus Group exposure, returned workflow_status manual_review_required, and generated a paid PDF artifact on Base.
- The bundled compliance tools have been exercised against the production MCP endpoint with settled transactions.
Example prompts
- Call server_capabilities to verify the server, payment model, and connection modes without paying first.
- Prepare an enhanced due diligence memo for a counterparty wallet set with compliance_edd_report.
- Forecast future OFAC exposure with compliance_exposure_forecast when the review needs probability and model limitations.
- Optimize a manual review queue with compliance_queue_optimize when exposure metadata and review budget are known.
- Screen a batch of treasury or counterparty wallets with wallet_ofac_batch and return the review signal.
- Screen 0x098B716B8Aaf21512996dC57EB0615e2383E2f96 and return a PDF with wallet_ofac_report.
- Screen 0x098B716B8Aaf21512996dC57EB0615e2383E2f96 and return the JSON report only with wallet_ofac_screen.
Connection
- Direct origin: https://api.aurelianflo.com/mcp
- Transport: streamable HTTP MCP.
- Payment: x402 with USDC on Base.
Direct origin
- Direct origin: codex mcp add aurelianflo --url https://api.aurelianflo.com/mcp
- No end-user OAuth or API key is required to connect.
- Call server_capabilities first to verify connectivity without paying.
Paid tool calls
- Use an x402-capable client and wallet to authorize paid calls with USDC on Base.
- The bundled compliance workflows are exposed as compliance_edd_report, compliance_exposure_forecast, compliance_queue_optimize, wallet_ofac_batch, and wallet_ofac_report.
- Connecting an MCP client does not automatically enable payment authorization.