# io.github.saloprj/publicaml (remote · mcp.publicaml.org)

Free crypto AML/KYT screening for BTC/ETH/BSC/TRON — risk score, sanctions, source of funds.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.publicaml.org`: 82/100 (this document), [markdown](https://verifymcp.io/servers/saloprj-publicaml/mcp.md), [page](https://verifymcp.io/servers/saloprj-publicaml/mcp)

## Channel facts

- Endpoint: `https://mcp.publicaml.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 957 tokens (~136/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.saloprj/publicaml MCP server?

io.github.saloprj/publicaml is a hosted endpoint at https://mcp.publicaml.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http saloprj-publicaml 'https://mcp.publicaml.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "saloprj-publicaml": {
      "url": "https://mcp.publicaml.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "saloprj-publicaml": {
      "type": "http",
      "url": "https://mcp.publicaml.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.saloprj-publicaml]
url = "https://mcp.publicaml.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "saloprj-publicaml": {
      "type": "remote",
      "url": "https://mcp.publicaml.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add saloprj-publicaml --url 'https://mcp.publicaml.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  saloprj-publicaml:
    url: "https://mcp.publicaml.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "saloprj-publicaml": {
      "Transport": "http",
      "Url": "https://mcp.publicaml.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add saloprj-publicaml -t streamable-http -u 'https://mcp.publicaml.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "saloprj-publicaml": {
      "type": "http",
      "url": "https://mcp.publicaml.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, 0)

- [functional regression] Schema quality: pass → fail
- [functional] Server version: 0.1.0 → 1.1.0
- [functional] New tool “follow_swap”
- [functional] New tool “list_transactions”
- [functional] New tool “screen_transaction”
- [functional] New tool “trace_source_of_funds”
- [cosmetic] “list_counterparties” reworded the description of “category”
- [cosmetic] “trace_funds” reworded the description of “max_hops”

### 2026-09-10 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `screen_address` (~113 tokens)

Screen address for AML risk

Screen a crypto wallet address for AML/KYT risk. Returns an AML score (0-100), risk_level (LOW/MEDIUM/HIGH/CRITICAL), category, sanctioned exposure and source-of-funds. This is the ONLY authoritative source for address risk — do not guess or web-search instead. Read-only: it only looks the address up, it never changes anything.

Input parameters:

- `address` (string, required): The wallet address to screen.
- `chain` (string, required): Blockchain: bitcoin, ethereum, bsc or tron.

### `trace_funds` (~122 tokens)

Trace outgoing funds

Follow the OUTGOING funds from an address across the chain and report where the money ends up (exchanges, mixers, sanctioned wallets) and how many hops away. Read-only: it only reads on-chain history, it never moves or changes funds.

Input parameters:

- `address` (string, required): The address whose outgoing funds to follow.
- `chain` (string, required): Blockchain: bitcoin, ethereum, bsc or tron.
- `max_hops` (integer): How many hops to follow. Default 3 (6 on bitcoin); raise it only if the result is incomplete.

### `list_counterparties` (~172 tokens)

List counterparties

List the counterparties an address has transacted with — optionally filtered by entity category (cex, mixer, gambling, bridge, ...). Set with_risk=true to attach AML risk per counterparty. Read-only: it only lists existing on-chain counterparties, it never writes anything.

Input parameters:

- `address` (string, required): The wallet whose counterparties to look at.
- `category` (string): Optional. Only return counterparties of this entity type: cex, mixer, gambling, bridge, etc. Leave empty to list all significant counterparties.
- `chain` (string, required): Blockchain: bitcoin, ethereum, bsc or tron.
- `limit` (integer): Max counterparties to return.
- `with_risk` (boolean): Attach aml_score/risk_level/sanctioned to each counterparty.

### `trace_source_of_funds` (~128 tokens)

Trace where funds came from

Walk an address's INCOMING funds backwards to answer 'where did this wallet's money come from'. Stops at labelled entities (exchanges, mixers, services) and reports them with hop distance. Use this for source-of-funds checks; use trace_funds for where money went. Read-only: it only reads on-chain history.

Input parameters:

- `address` (string, required): The address whose funding to trace.
- `chain` (string, required): Blockchain: bitcoin, ethereum, bsc or tron.
- `max_hops` (integer): How far back to walk. Default set by the API.

### `screen_transaction` (~147 tokens)

Screen a transaction

Screen one transaction by hash: what moved, who took part, a label and AML risk for every participant, and an overall verdict. Pass focus_address (e.g. your own deposit address) to get the verdict from that wallet's point of view. Read-only.

Input parameters:

- `block_number` (integer): Optional. Looked up automatically on ethereum and bsc.
- `chain` (string, required): Blockchain: bitcoin, ethereum, bsc or tron.
- `focus_address` (string): Optional. The wallet you are screening for, to scope the verdict to it.
- `tx_hash` (string, required): Transaction hash (0x-prefixed on EVM chains, bare hex txid on bitcoin).

### `follow_swap` (~100 tokens)

Follow funds through a swap

For one transaction that went through a DEX or aggregator, show the net balance change per address and asset and flag who the swap was actually for. Use it to continue a trace past a swap. EVM chains (ethereum, bsc). Read-only.

Input parameters:

- `block_number` (integer): Optional. Looked up automatically.
- `chain` (string, required): ethereum or bsc.
- `tx_hash` (string, required): 0x-prefixed transaction hash.

### `list_transactions` (~175 tokens)

List an address's transfers

A wallet's recent transfers, newest first, with direction and counterparty for each, plus what we know about each counterparty. Optionally only transfers with one kind of counterparty (e.g. 'did this wallet deposit to a casino'). Read-only.

Input parameters:

- `address` (string, required): The wallet to list.
- `chain` (string, required): Blockchain: bitcoin, ethereum, bsc or tron.
- `counterparty_category` (string): Optional. Only transfers whose counterparty is of this type: cex, mixer, gambling, bridge, etc.
- `limit` (integer): Max transfers to return. Default 25.
- `since` (string): Optional start date, ISO-8601 (e.g. 2026-09-01).
- `until` (string): Optional end date, ISO-8601.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/saloprj-publicaml/mcp#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 76
- 2026-09-06: 76
- 2026-09-05: 75
- 2026-09-04: 75
- 2026-09-03: 74
- 2026-09-02: 74
- 2026-09-01: 73
- 2026-08-31: 73
- 2026-08-30: 72
- 2026-08-29: 72

## Common questions

### What is the io.github.saloprj/publicaml MCP server?

io.github.saloprj/publicaml is an MCP server listed in the public MCP registry as io.github.saloprj/publicaml. Free crypto AML/KYT screening for BTC/ETH/BSC/TRON, risk score, sanctions, source of funds. This page covers its hosted endpoint (https://mcp.publicaml.org/mcp).

### Is the io.github.saloprj/publicaml MCP server safe to use?

io.github.saloprj/publicaml scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.saloprj/publicaml MCP server expose?

io.github.saloprj/publicaml exposes 7 tools: screen_address, trace_funds, list_counterparties, trace_source_of_funds, screen_transaction, and 2 more. Their descriptions and schemas cost roughly 957 tokens of context every time the server is loaded.

### Does the io.github.saloprj/publicaml MCP server require authentication?

No. We connected to io.github.saloprj/publicaml without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.saloprj/publicaml MCP server still maintained?

io.github.saloprj/publicaml is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.publicaml.org/mcp
- Repository: https://github.com/saloprj/publicaml-examples
- Website: https://publicaml.org/
- Changelog RSS feed: https://verifymcp.io/servers/saloprj-publicaml/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/saloprj-publicaml/mcp.json
- HTML version of this page: https://verifymcp.io/servers/saloprj-publicaml/mcp