Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
AurelianFlo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Remote MCP server for OFAC screening, EDD memos, exposure forecasts, queues, and reports.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aurelianflo-mcp https://api.aurelianflo.com/mcp
# 2 — ask your agent for something these tools do
# server_capabilities, queue_saved_list, report_saved_retrieve and 8 more
AurelianFlo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AUAll 1 server
aurelianflo1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http aurelianflo-mcp https://api.aurelianflo.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Free first-call capability and connection check for AurelianFlo; use it before paid tools to inspect OFAC screening workflows, access modes, and x402 payment requirements.
No parameter schema on file.
Free read-only saved queue status utility for agents asking whether AurelianFlo can list prior compliance_queue_optimize results. AurelianFlo does not persist saved queues server-side; rerun compliance_queue_optimize with the original review_items to recreate a queue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_reference | string | no | Optional client-side case reference to echo in the status response. |
| limit | integer | no | Maximum saved queue records to list if server-side queue persistence becomes configured. |
Free read-only past report retrieval status utility for agents asking about previously generated reports. AurelianFlo returns report artifacts inline as artifact.contentBase64 and does not persist hosted report files server-side.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | string | no | Optional client-side report or case identifier to echo in the retrieval status response. |
| file_name | string | no | Optional file name from a prior artifact response. |
| settlement_tx | string | no | Optional x402 settlement transaction hash associated with a prior paid report call. |
Run a paid OFAC screening report for one crypto wallet and return structured JSON or an inline PDF/DOCX artifact. Use wallet_ofac_screen for a quick single-address status check, or wallet_ofac_batch for multiple addresses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Crypto wallet address to screen against OFAC SDN digital currency address designations. |
| asset | string | no | Optional asset or network ticker filter such as ETH, USDC, XBT, TRX, ARB, or BSC. |
| output_format | string | yes | Select json for the structured report payload or pdf|docx for a generated artifact. |
Screen one crypto wallet address against OFAC SDN digital currency designations and return exact hits, sanctioned entity metadata, asset coverage, and a manual-review signal. Use this for one-off status checks; use wallet_ofac_report for PDF/DOCX output or wallet_ofac_batch for multiple addresses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Crypto wallet address to screen against OFAC SDN digital currency address designations. |
| asset | string | no | Optional asset or network ticker filter such as ETH, USDC, XBT, TRX, ARB, or BSC. |
Screen 1-100 crypto wallet addresses against OFAC SDN digital currency designations before payout, onboarding, or treasury movement, returning per-wallet results plus a batch-level proceed-or-pause decision. Use this instead of wallet_ofac_screen for multiple addresses; use compliance_edd_report when a formal memo is needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| addresses | array | yes | Crypto wallet addresses to screen against OFAC SDN digital currency address designations. |
| asset | string | no | Optional asset or network ticker filter such as ETH, USDC, XBT, TRX, ARB, or BSC. |
Build a paid enhanced due diligence memo for a wallet set using exact-match OFAC screening, sanctions evidence, and follow-up actions, returning structured JSON or an inline PDF/DOCX artifact. Use this for case handoff; use wallet_ofac_batch for screening-only results or report_pdf_generate/report_docx_generate only when the report payload already exists.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject_name | string | yes | Human-readable subject or counterparty name for the memo. |
| case_name | string | no | Optional case or review title shown in the memo. |
| review_reason | string | no | Optional reason the EDD memo is being prepared. |
| jurisdiction | string | no | Optional jurisdiction or operating region for the case. |
| requested_by | string | no | Optional requester, owner, or reviewing team. |
| reference_id | string | no | Optional internal case or review reference. |
| output_format | string | yes | Select json for the structured memo payload or pdf|docx for a generated artifact. |
| artifact_only | boolean | no | When output_format is pdf or docx, return a compact artifact-first response without the full memo payload. |
| addresses | array | yes | Crypto wallet addresses to screen for OFAC sanctions exposure and include in the enhanced due diligence memo. |
| asset | string | no | Optional asset or network ticker filter such as ETH, USDC, XBT, TRX, ARB, or BSC. |
Forecast future OFAC wallet exposure for a wallet set using stored OFAC snapshot diffs when available, listedOn backfill when honest, or an explicit caller prior; returns current exact-match baseline, metadata-weighted per-wallet risk, and report-shaped output. Use this when current screening is not enough; use wallet_ofac_batch for current hit status only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| addresses | array | yes | Wallet addresses to forecast for future OFAC exact-match exposure. |
| address_metadata | array | no | Optional per-address business metadata used to weight exposure hazard. |
| asset | string | no | Optional asset or network ticker filter such as ETH, USDC, XBT, TRX, ARB, or BSC. |
| horizon_days | integer | no | Forecast horizon in days. |
| iterations | integer | no | Forecast trial count. |
| target | object | no | Target event for the forecast probability. |
| tier_weights | object | no | Relationship tier weight overrides. |
| priors | object | no | Explicit prior assumptions used only when overriding OFAC history cadence. |
| title | string | no | Optional report title. |
| summary_focus | string | no | Optional summary emphasis or focus area. |
Optimize a compliance review queue using current OFAC exact matches, future exposure probabilities, exposure value, relationship tier, recency, and reviewer capacity. Use this when review_items and review_budget are known; use compliance_exposure_forecast for probability-only analysis or compliance_edd_report for a case memo.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| review_items | array | yes | Wallet review items with per-address metadata required for queue optimization. |
| review_budget | integer | yes | Number of items a reviewer can handle in the next review window. |
| objective | string | no | Optimization objective. |
| asset | string | no | Optional asset or network ticker filter such as ETH, USDC, XBT, TRX, ARB, or BSC. |
| horizon_days | integer | no | Forecast horizon in days. |
| iterations | integer | no | Forecast trial count. |
| tier_weights | object | no | Relationship tier weight overrides. |
| priors | object | no | Explicit prior assumptions used only when overriding OFAC history cadence. |
| title | string | no | Optional report title. |
| summary_focus | string | no | Optional summary emphasis or focus area. |
Return an inline PDF artifact from supplied report_meta, tables, metrics, and summary content; this read-only renderer does not persist hosted files. Use this only when a structured report payload already exists; use report_docx_generate for editable Word output or compliance_edd_report to build the memo first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_meta | object | yes | — |
| executive_summary | array | no | Optional executive summary bullets. |
| headline_metrics | array | no | Optional headline metrics rendered near the top of the report. |
| tables | object | yes | Named tables rendered into the report artifact. |
| export_artifacts | object | no | Optional prior export metadata carried alongside the report payload. |
| result | object | no | Optional raw result payload attached for audit or downstream use. |
Return an inline DOCX artifact from supplied report_meta, tables, metrics, and summary content; this read-only renderer does not persist hosted files. Use this only when a structured report payload already exists; use report_pdf_generate for fixed-layout output or compliance_edd_report to build the memo first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_meta | object | yes | — |
| executive_summary | array | no | Optional executive summary bullets. |
| headline_metrics | array | no | Optional headline metrics rendered near the top of the report. |
| tables | object | yes | Named tables rendered into the report artifact. |
| export_artifacts | object | no | Optional prior export metadata carried alongside the report payload. |
| result | object | no | Optional raw result payload attached for audit or downstream use. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AurelianFlo or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.4.0.
0.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AurelianFlo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.