Skip to content

aml MCP server

io.tooloracle/amltooloracle.iostreamable-httpv1.0.0Scanned

AMLOracle — 12-tool AML/CFT MCP: 87k sanctions names, PEP screening, adverse media, SAR/STR.

12 tools: 1 do something that can't be undone, 10 change things and 1 only read.

Tools: 0 delete, 1 irreversible, 10 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 aml MCP server can do

The aml MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (transaction_risk) and create or change data (10 tools: sanctions_screen, sanctions_detail, pep_check, adverse_media and 6 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data 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.

Last scanned Nov 17, 2026, version 1.0.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.

12 tools

Can't be undone 1Claude Code: ask
  • transaction_riskAML transaction risk scoring: amount, corridor, sender screening.No findings

    Why it is in this group

    • The input carries an amount (input.amount) and a currency, so it moves money.
    Description, as the server wrote it
    AML transaction risk scoring: amount, corridor, sender screening. AMLR Art. 35+82.
Changes things 10Claude Code: ask
  • adverse_mediaNegative news screening: fraud, money laundering, corruption, sanctions.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.
    Description, as the server wrote it
    Negative news screening: fraud, money laundering, corruption, sanctions. AMLR Art. 55 ongoing monitoring.
  • aml_newsAMLR / AMLA / AMLD6 regulatory news.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.
    Description, as the server wrote it
    AMLR / AMLA / AMLD6 regulatory news. Topics: general, amla, amlr, sanctions, crypto_aml, fatf, de_geldwaesche, pep, kyc, str.
  • amlr_calendarAMLR compliance milestones.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.
    Description, as the server wrote it
    AMLR compliance milestones. Key: 1 July 2026 full application, €10k cash limit, crypto Travel Rule €0.
  • country_riskCountry risk assessment: FATF Blacklist, Greylist, EU High-Risk.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.
    Description, as the server wrote it
    Country risk assessment: FATF Blacklist, Greylist, EU High-Risk. AMLR Art. 16+18.
  • health_checkAMLOracle server status, backend checks, and watchlist cache status.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.
    Description, as the server wrote it
    AMLOracle server status, backend checks, and watchlist cache status.
  • kyc_bundleFull KYC in one call: Sanctions + PEP + Adverse Media + Country Risk.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.
    Description, as the server wrote it
    Full KYC in one call: Sanctions + PEP + Adverse Media + Country Risk. Returns overall risk level and AMLR decision.
  • pep_checkPEP (Politically Exposed Person) check via Wikidata.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.
    Description, as the server wrote it
    PEP (Politically Exposed Person) check via Wikidata. AMLR Art. 22 enhanced CDD for PEPs.
  • sanctions_detailFull entity record for sanctions hit.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.
    Description, as the server wrote it
    Full entity record for sanctions hit. Returns UN XML detail, aliases, nationality, designation.
  • sanctions_screenScreen any name against EU FSF (14k), OFAC SDN (69k), UN SC (3k), Interpol (13k) watchlists.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.
    Description, as the server wrote it
    Screen any name against EU FSF (14k), OFAC SDN (69k), UN SC (3k), Interpol (13k) watchlists. AMLR Art. 35.
  • watchlist_updateCheck watchlist freshness and reload from OpenSanctions.No findings

    Why it is in this group

    • The name "watchlist_update" says "update": a word for a change.
    Description, as the server wrote it
    Check watchlist freshness and reload from OpenSanctions. Use force_reload=true to refresh cache.
Only reads 1Show 1 read-only tool
  • ubo_lookupUltimate Beneficial Owner (UBO) identification via GLEIF LEI ownership register.No findings

    Why it is in this group

    • The name "ubo_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    Ultimate Beneficial Owner (UBO) identification via GLEIF LEI ownership register. AMLR Art. 42.

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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, 19:23 UTC, unchanged since Oct 22, 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
11
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://tooloracle.io/.well-known/oauth-protected-resource/aml/mcp
Authorization servers
https://feedoracle.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://tooloracle.io/aml/mcp/: tools/list returned 12 tools to an anonymous client, including transaction_risk (irreversible), sanctions_screen (write), sanctions_detail (write), pep_check (write), adverse_media (write) and 6 more

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http aml https://tooloracle.io/aml/mcp/
claude mcp add --transport http aml https://tooloracle.io/aml/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__aml__ubo_lookup"
    ],
    "ask": [
      "mcp__aml__sanctions_screen",
      "mcp__aml__sanctions_detail",
      "mcp__aml__pep_check",
      "mcp__aml__adverse_media",
      "mcp__aml__country_risk",
      "mcp__aml__kyc_bundle",
      "mcp__aml__transaction_risk",
      "mcp__aml__aml_news",
      "mcp__aml__amlr_calendar",
      "mcp__aml__watchlist_update",
      "mcp__aml__health_check"
    ],
    "deny": []
  }
}

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 aml. Review it before you use it.

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/io.tooloracle/aml/verify?hash=5c4c0c7d4b523295ea14547d121f314c6c53b0d776f025e02d33f6a394dc919a" | jq -e '.changed == false'

Pinned hash 5c4c0c7d4b52, from Nov 17, 2026, 20:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.tooloracle/aml/changes.xml

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

Badge

Anlyon Radar badge for io.tooloracle/aml
[![Anlyon Radar](https://radar.anlyon.com/badge/io.tooloracle/aml.svg)](https://radar.anlyon.com/servers/io.tooloracle/aml)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.

aml MCP server: questions and answers

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

Is the aml MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 11 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 aml MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the aml MCP server do things that cannot be undone?

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

What tools does the aml MCP server have?

12 tools: 1 irreversible, 10 write, 1 read. transaction_risk, sanctions_screen, sanctions_detail, pep_check, adverse_media, country_risk, kyc_bundle, aml_news and 4 more.

Does the aml MCP server need sign-in or OAuth?

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

Does the aml MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the aml MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.