
AurelianFlo MCP server
Which servers in the official MCP registry are AurelianFlo's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.aurelianflo/coreverified in the MCP registry
The registry name sits under aurelianflo.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools11
- Server calls itselfAurelianFlo
- Server version0.4.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 140 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer146 ms
- Space in an agent's context≈ 5,071 tokensthe definitions of all its tools (11), which an agent carries on every turn
- Tool definitionsA · 97 of 100
- Typed results11 of 11 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 11
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
server_capabilitiesFree first-call capability and connection check for AurelianFlo; use it before paid tools to inspect OFAC screening workflows, access modes, and x402 payment requirements.
queue_saved_listFree 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…
report_saved_retrieveFree 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.
wallet_ofac_reportRun 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.
wallet_ofac_screenScreen 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…
wallet_ofac_batchScreen 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…
compliance_edd_reportBuild 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…
compliance_exposure_forecastForecast 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…
compliance_queue_optimizeOptimize 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…
report_pdf_generateReturn 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…
report_docx_generateReturn 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"core": {
"type": "http",
"url": "https://api.aurelianflo.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http aurelianflo https://api.aurelianflo.com/mcpclaude.ai, ChatGPT and other clients: add https://api.aurelianflo.com/mcp as a custom connector in the settings.
OpenAPI spec
10 paths, read 2026-10-24. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.