Skip to content

AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server

com.aurelianflo/coreaurelianflo.comstreamable-httpv0.9.0Scanned

OFAC wallet and name screening, EDD memos, exposure reports, review queues, watchlists. Free to use.

22 tools: 4 can delete or cancel things, 1 do something that can't be undone, 12 change things and 5 only read.

Tools: 4 delete, 1 irreversible, 12 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 7
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server can do

The AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server is published by aurelianflo.com, a domain the MCP Registry verified. It has 22 tools. It can delete or cancel things (4 tools: saved_results_delete, wallet_watchlist_remove, wallet_watchlist_alerts and account_api_key_revoke), do things that cannot be undone, such as sending, paying or publishing (wallet_watchlist_test_alert) and create or change data (12 tools: server_capabilities, wallet_screen, compliance_edd_report, compliance_exposure_report and 8 more). 5 tools only read.

1 tool reads private data (wallet_watchlist_events); 7 tools bring in text other people can write (wallet_screen, compliance_edd_report, compliance_exposure_report and 4 more); 1 tool can send data out of your system (wallet_watchlist_test_alert). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.9.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

22 tools

Deletes or cancels 4Claude Code: deny
  • account_api_key_revokeRevoke one of your API keys by its first 12 characters (key_prefix), as listed by account_api_keys, or every key on the account at once (all: true).No findings

    Why it is in this group

    • The name "account_api_key_revoke" says "revoke": a word for removing or ending something.
    • The description says "cannot be restored".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke one of your API keys by its first 12 characters (key_prefix), as listed by account_api_keys, or every key on the account at once (all: true). A revoked key stops working immediately and cannot be restored. Scoped to your account: needs an email sign-in at /mcp/account. A request made with an API key cannot revoke keys. Free.

    Annotations the server declares

    • title: Revoke API Key
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • saved_results_deletePermanently delete one saved result from your account by its ID.No findings

    Why it is in this group

    • The name "saved_results_delete" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete one saved result from your account by its ID. This cannot be undone. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Delete Saved Result
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • wallet_watchlist_alertsChange how watchlist alerts reach you: set or clear the alert webhook, and turn email alerts on or off.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Change how watchlist alerts reach you: set or clear the alert webhook, and turn email alerts on or off. Setting a webhook returns its signing secret once. Setting a webhook again replaces the webhook and its signing secret with a new one, and the earlier secret stops working, so call it again only when you mean to. An empty webhook_url removes the webhook. To read the current settings (webhook URL and whether email alerts are on), use wallet_watchlist. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Watchlist Alert Settings
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • wallet_watchlist_removeStop watching wallet addresses.No findings

    Why it is in this group

    • The name "wallet_watchlist_remove" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Stop watching wallet addresses. They are removed from your watchlist and no longer raise alerts or cost anything. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Remove from Watchlist
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • wallet_watchlist_test_alertSend one signed test event (type watchlist.test) to your alert webhook and, if email alerts are on, a test email, and report whether each was delivered.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send one signed test event (type watchlist.test) to your alert webhook and, if email alerts are on, a test email, and report whether each was delivered. Nothing is retried. Limited to 5 per hour. With no webhook set and email alerts off, nothing is sent and the result says what to set up. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Send Test Alert
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 12Claude Code: ask
  • account_api_key_createCreate an API key for your account.No findings

    Why it is in this group

    • The name "account_api_key_create" says "create": a word for a change.
    Description, as the server wrote it
    Create an API key for your account. The key is returned once and cannot be shown again, so give it to the user straight away and do not store or repeat it. An account can hold up to 5 active keys. A key gives the same free access as signing in, with the same daily limits. Scoped to your account: needs an email sign-in at /mcp/account. A request made with an API key cannot create keys. Free.

    Annotations the server declares

    • title: Create API Key
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • compliance_edd_reportBuild an enhanced due diligence memo for a subject and its wallets: exact-match OFAC wallet screening, subject-name screening against sanctioned parties, sanctions evidence, and fo…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Build an enhanced due diligence memo for a subject and its wallets: exact-match OFAC wallet screening, subject-name screening against sanctioned parties, sanctions evidence, and follow-up actions, returned as structured JSON or an inline PDF/DOCX artifact. Wallet addresses are optional: without them the memo covers the subject name only and says no wallets were supplied. Use this for case handoff; use wallet_screen for screening-only results. To keep the memo in your account, call saved_results_save with its screening_id. Price without an account: $0.25 per call.

    Annotations the server declares

    • title: EDD Report
    • readOnlyHint: true
    • openWorldHint: true
  • compliance_exposure_reportReport each wallet's exposure to sanctioned addresses from evidence: whether it is listed now, and whether its own on-chain transfers in the lookback period were sent to or receive…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Report each wallet's exposure to sanctioned addresses from evidence: whether it is listed now, and whether its own on-chain transfers in the lookback period were sent to or received from listed addresses. Every wallet is read, including wallets that are already listed, so a listed wallet still shows its counterparties. Each wallet comes back as listed, exposed, none found in what was read, or not established, with the listed parties, transfer counts and a coverage block that says what was read and whether the read was partial. Use chains to read EVM wallets on Ethereum, Base, Arbitrum, Optimism, Polygon or Gnosis, and depth 2 to also check counterparties of counterparties. Listed means an exact match on the OFAC SDN list. It does not predict future listings. Up to 20 wallets per call. To keep the report in your account, call saved_results_save with its screening_id. Price without an account: $0.04 per wallet at depth 1, or $0.14 per wallet at depth 2 (the same as the indirect exposure add-on on wallet_screen), up to 20 wallets per call. PDF/DOCX output adds $0.05.

    Annotations the server declares

    • title: Exposure Report
    • readOnlyHint: true
    • openWorldHint: true
  • compliance_queue_optimizeOrder a backlog of wallets for manual review.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Order a backlog of wallets for manual review. Wallets that are on the sanctions list now come first and show no score; the rest are ordered by a priority score built from the figures you supply (exposure, relationship tier, recent activity, policy priority), and from exposure report rows if you pass them as addresses_from_exposure. Exposure and tier are optional: a figure you leave out is treated as unknown, and the row says so. Each row says why it sits where it does, and a line marks where your review capacity runs out. It does not predict future listings. Use compliance_exposure_report for on-chain evidence about specific wallets. Up to 100 wallets per call, counting review_items and addresses_from_exposure together. To keep the queue in your account, call saved_results_save with its screening_id. Price without an account: $0.05 per call, whatever the number of wallets. PDF/DOCX output adds $0.05.

    Annotations the server declares

    • title: Review Queue
    • readOnlyHint: true
    • openWorldHint: false
  • sanctions_party_screenScreen 1-100 person, company or vessel names against the OFAC SDN, UK, EU and UN sanctions lists, without needing a wallet.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Screen 1-100 person, company or vessel names against the OFAC SDN, UK, EU and UN sanctions lists, without needing a wallet. Matching is token-aware and fuzzy, over listed names and aliases. Optional type, country, date of birth and ID number are compared with each candidate's listed record, and every candidate reports which identifiers agree, disagree or were not available, plus its score components, so a discounted candidate can be documented. Each name gets a status: match (score 0.95 or higher), possible (at or above min_score, default 0.88) or no_match, with up to 5 candidates. no_match means no listed party scored at or above the threshold on the lists checked; it does not clear the name. Results carry a screening_id and signed provenance, and are leads for human review. Price without an account: $0.01 per name or alias, at most $0.10 per call.

    Annotations the server declares

    • title: Sanctions Party Screen
    • readOnlyHint: true
    • openWorldHint: true
  • saved_results_exportExport results you saved as one JSON bundle for a case file or an audit.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Export results you saved as one JSON bundle for a case file or an audit. Each entry has the result's data, its provenance (signature and the sanctions list version, with the list's SHA-256) and a SHA-256 for the entry, and the bundle has a manifest listing them. Filter by case_reference, tool or saved date. Large exports come in pages: pass next_cursor back as cursor. Stored PDF and Word files are left out of the bundle. An account lists its 1,000 most recent saved results, so older ones are not in the export. Check a bundle offline with scripts/verify_result.js. Read-only. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Export Saved Results
    • readOnlyHint: true
    • openWorldHint: false
  • saved_results_saveKeep a result you just produced in your account, by its screening_id, so you can list it, reopen it and verify it later.No findings

    Why it is in this group

    • The name "saved_results_save" says "save": a word for a change.
    Description, as the server wrote it
    Keep a result you just produced in your account, by its screening_id, so you can list it, reopen it and verify it later. Works for a screening or memo made by this account in the last 15 minutes; after that, run it again. The free test addresses produce test results, which cannot be saved. Saving the same result twice does nothing the second time. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Save Result
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • screening_verifyFree check that a stored AurelianFlo screening, batch or EDD result is authentic and unchanged.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free check that a stored AurelianFlo screening, batch or EDD result is authentic and unchanged. Pass the result's data and provenance exactly as returned (any edit fails verification), or pass its screening_id to verify a result stored for your account, which needs sign-in or an API key.

    Annotations the server declares

    • title: Verify Screening Result
    • readOnlyHint: true
    • openWorldHint: false
  • server_capabilitiesFree first-call capability and connection check for AurelianFlo; use it first to see the tools, your daily limits (or prices without an account), free test inputs, sample responses…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free first-call capability and connection check for AurelianFlo; use it first to see the tools, your daily limits (or prices without an account), free test inputs, sample responses, and how to sign in.

    Annotations the server declares

    • title: Server Capabilities
    • readOnlyHint: true
    • openWorldHint: false
  • wallet_payee_checkPre-payment check for one wallet address: a short yes/no for an agent or payment flow that is about to send funds.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Pre-payment check for one wallet address: a short yes/no for an agent or payment flow that is about to send funds. Returns decision block, no_exact_match or invalid_address, whether the address is listed, the listed entity and programs when it is, the OFAC SDN list date and hash, a screening_id and a signature reference. It uses the same exact-match lookup as wallet_screen, so the two never disagree. no_exact_match means the address is not on the list checked; it is not a clearance. Use wallet_screen for several addresses, other lists or a report. Price without an account: $0.005 per call.

    Annotations the server declares

    • title: Wallet Payee Check
    • readOnlyHint: true
    • openWorldHint: true
  • wallet_screenScreen 1-100 crypto wallet addresses against OFAC sanctions lists (SDN by default).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Screen 1-100 crypto wallet addresses against OFAC sanctions lists (SDN by default). Returns exact matches with sanctioned-entity details, address validation, a proceed-or-review decision and signed provenance. Every result carries a verdict that names the lists checked, their dates and what to do next. Optional: PDF/DOCX report (output_format) and, for a single EVM, TRON or Bitcoin address, indirect exposure through counterparties (exposure_depth). To keep the result in your account, call saved_results_save with its screening_id. Price without an account: $0.01 per address, at most $0.10 per call (10-100 addresses cost $0.10). PDF/DOCX output adds $0.05. Indirect exposure adds $0.04 (exposure_depth 1) or $0.14 (exposure_depth 2).

    Annotations the server declares

    • title: Wallet Screen
    • readOnlyHint: true
    • openWorldHint: true
  • wallet_watchlist_addStart watching wallet addresses, so you are alerted (signed webhook and/or email) when one is added to a sanctions list.No findings

    Why it is in this group

    • The name "wallet_watchlist_add" says "add": a word for a change.
    Description, as the server wrote it
    Start watching wallet addresses, so you are alerted (signed webhook and/or email) when one is added to a sanctions list. Free: an account can watch up to 25 addresses. Scoped to your account: needs sign-in (/mcp/account) or an API key.

    Annotations the server declares

    • title: Add to Watchlist
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • account_api_keysList the API keys on your account: each key's first 12 characters and when it was created (a key issued before keys were listed shows no date, and appears after its first use).No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the API keys on your account: each key's first 12 characters and when it was created (a key issued before keys were listed shows no date, and appears after its first use). The keys themselves are never shown. Read-only. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: List API Keys
    • readOnlyHint: true
    • openWorldHint: false
  • sanctions_list_changesList the crypto addresses added to or removed from the OFAC SDN list since a date, with each party's name, programs and asset, and the two list versions compared (publication date,…No findings

    Why it is in this group

    • The name "sanctions_list_changes" says "list": a word for reading.
    Description, as the server wrote it
    List the crypto addresses added to or removed from the OFAC SDN list since a date, with each party's name, programs and asset, and the two list versions compared (publication date, hash, address count). Read-only. Built from the daily list snapshots this server stores, looks back at most 90 days, and states what period the stored history covers. Free, no sign-in needed.

    Annotations the server declares

    • title: Sanctions List Changes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • saved_resultsList the results saved in your account (screening, EDD memo, exposure report or queue), or fetch one by its screening_id.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the results saved in your account (screening, EDD memo, exposure report or queue), or fetch one by its screening_id. Each list row gives the screening_id, tool, case reference, subject or first address, address count, headline status and save date. Read-only. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Saved Results
    • readOnlyHint: true
    • openWorldHint: false
  • wallet_watchlistShow your watchlist: the wallet addresses being watched, any that have since been listed, and the alert settings.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show your watchlist: the wallet addresses being watched, any that have since been listed, and the alert settings. Read-only. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Watchlist
    • readOnlyHint: true
    • openWorldHint: false
  • wallet_watchlist_eventsShow the log of what your watchlist did, newest first: each check (when, against which list version, how many addresses), each alert raised (address and listed party), and each del…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "show" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "show" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Show the log of what your watchlist did, newest first: each check (when, against which list version, how many addresses), each alert raised (address and listed party), and each delivery attempt (webhook delivered, retry scheduled, dropped, email sent, email failed). Read-only. Keeps the last 300 entries. Scoped to your account: needs sign-in (/mcp/account) or an API key. Free.

    Annotations the server declares

    • title: Watchlist Log
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

7 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__core__wallet_watchlist_test_alert"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:34 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
17
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 17 tools that change things (4 destructive, 1 irreversible, 12 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.aurelianflo.com/mcp: tools/list returned 22 tools to an anonymous client, including saved_results_delete (destructive), wallet_watchlist_remove (destructive), wallet_watchlist_alerts (destructive), account_api_key_revoke (destructive), wallet_watchlist_test_alert (irreversible) and 12 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 8 to 17
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 9 to 8

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 17.View diff
    • Tools that change things, listed without credentials: 8 to 17
  2. Tools10 added, 12 changed.+10 added~12 changedView diff
  3. Tools7 changed.~7 changedView diff
  4. Tools1 added, 1 removed, 1 changed.+1 added−1 removed~1 changedView diff
  5. Tools4 added, 4 changed.+4 added~4 changedView diff
  6. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 8.View diff
    • Tools that change things, listed without credentials: 9 to 8
  7. Tools4 added, 7 removed, 4 changed.+4 added−7 removed~4 changedView diff

Install

Pinned to version 0.9.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http core https://api.aurelianflo.com/mcp
claude mcp add --transport http core https://api.aurelianflo.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__core__saved_results",
      "mcp__core__wallet_watchlist",
      "mcp__core__sanctions_list_changes",
      "mcp__core__wallet_watchlist_events",
      "mcp__core__account_api_keys"
    ],
    "ask": [
      "mcp__core__server_capabilities",
      "mcp__core__wallet_screen",
      "mcp__core__compliance_edd_report",
      "mcp__core__compliance_exposure_report",
      "mcp__core__compliance_queue_optimize",
      "mcp__core__screening_verify",
      "mcp__core__wallet_watchlist_add",
      "mcp__core__saved_results_save",
      "mcp__core__sanctions_party_screen",
      "mcp__core__wallet_payee_check",
      "mcp__core__wallet_watchlist_test_alert",
      "mcp__core__account_api_key_create",
      "mcp__core__saved_results_export"
    ],
    "deny": [
      "mcp__core__saved_results_delete",
      "mcp__core__wallet_watchlist_remove",
      "mcp__core__wallet_watchlist_alerts",
      "mcp__core__account_api_key_revoke"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as core. Review it before you use it.

Capability tags behind 7 rules
  • mcp__core__wallet_screen untrusted-input
  • mcp__core__compliance_edd_report untrusted-input
  • mcp__core__compliance_exposure_report untrusted-input
  • mcp__core__sanctions_party_screen untrusted-input
  • mcp__core__wallet_payee_check untrusted-input
  • mcp__core__wallet_watchlist_events private-data, untrusted-input
  • mcp__core__wallet_watchlist_test_alert untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.aurelianflo/core/verify?hash=118d555205345e550bb6d2b74f85038677cd78729390ef839356d0a0b9479297" | jq -e '.changed == false'

Pinned hash 118d55520534, from Nov 15, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.aurelianflo/core/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.aurelianflo/core
[![Anlyon Radar](https://radar.anlyon.com/badge/com.aurelianflo/core.svg)](https://radar.anlyon.com/servers/com.aurelianflo/core)

Source: MCP Registry · repository. Synced Nov 15, 2026, 02:17 UTC.

AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server safe?

No scan can promise that. What its definitions show: 22 tools, 17 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server delete data?

Yes. 4 tools can delete, cancel or revoke something: saved_results_delete, wallet_watchlist_remove, wallet_watchlist_alerts and account_api_key_revoke.

Can the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: wallet_watchlist_test_alert.

What tools does the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server have?

22 tools: 4 destructive, 1 irreversible, 12 write, 5 read. saved_results_delete, wallet_watchlist_remove, wallet_watchlist_alerts, account_api_key_revoke, wallet_watchlist_test_alert, server_capabilities, wallet_screen, compliance_edd_report and 14 more.

Does the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): wallet_watchlist_test_alert.

Has the AurelianFlo: Sanctions Screening for Crypto Wallets and Names MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.