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 with direct and Smithery-hosted modes.
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 modes

Direct origin: https://api.aurelianflo.com/mcp
Smithery-hosted gateway: https://core--aurelianflo.run.tools
Transport: streamable HTTP MCP.
Payment: x402 with USDC on Base.

Direct origin

Direct origin: codex mcp add aurelianflo --url https://api.aurelianflo.com/mcp
Use the origin directly for paid execution.
Use the origin directly when the client does not implement Smithery's hosted OAuth flow.

Smithery hosted

Smithery listing: aurelianflo/core
CLI connection: smithery mcp add aurelianflo/core
Hosted gateway: codex mcp add aurelianflo-core --url https://core--aurelianflo.run.tools
Use server.capabilities first on the Smithery-hosted connection.
The bundled compliance workflows are exposed as compliance.edd.report, compliance.exposure.forecast, compliance.queue.optimize, wallet.ofac.batch, and wallet.ofac.report.
Paid execution is currently available through the direct origin at https://api.aurelianflo.com/mcp.
OAuth-capable clients should follow the Smithery authorization URL when the hosted gateway returns auth_required.
If Smithery's Windows client installer handoff fails, add the hosted gateway or the direct origin with codex mcp add ... --url ... instead of relying on --client codex.