io.github.saloprj/publicaml
REMOTE · MCP.PUBLICAML.ORG · SCANNED SEP 20
Free crypto AML/KYT screening for BTC/ETH/BSC/TRON — risk score, sanctions, source of funds.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.publicaml.org
claude mcp add --transport http saloprj-publicaml 'https://mcp.publicaml.org/mcp'
{
"mcpServers": {
"saloprj-publicaml": {
"url": "https://mcp.publicaml.org/mcp"
}
}
} {
"servers": {
"saloprj-publicaml": {
"type": "http",
"url": "https://mcp.publicaml.org/mcp"
}
}
} [mcp_servers.saloprj-publicaml] url = "https://mcp.publicaml.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"saloprj-publicaml": {
"type": "remote",
"url": "https://mcp.publicaml.org/mcp",
"enabled": true
}
}
} openclaw mcp add saloprj-publicaml --url 'https://mcp.publicaml.org/mcp' --transport streamable-http
mcp_servers:
saloprj-publicaml:
url: "https://mcp.publicaml.org/mcp" {
"McpServers": {
"saloprj-publicaml": {
"Transport": "http",
"Url": "https://mcp.publicaml.org/mcp"
}
}
} assistant mcp add saloprj-publicaml -t streamable-http -u 'https://mcp.publicaml.org/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 0
- 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” functional
- “list_counterparties” reworded the description of “category” cosmetic
- “trace_funds” reworded the description of “max_hops” cosmetic
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.publicaml.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=publicaml.org | CN=WE1,O=Google Trust Services,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ca21b47a1c7f6c3d0eced61ecd2c3300 |
| SANs: publicaml.org, *.publicaml.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.publicaml.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| publicaml.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.publicaml.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.publicaml.org/mcp | HTTPS enforced | 301 | https://mcp.publicaml.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
follow_swap Follow funds through a swap ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| block_number | integer | – | Optional. Looked up automatically. |
| chain | string | yes | ethereum or bsc. |
| tx_hash | string | yes | 0x-prefixed transaction hash. |
No output schema declared.
No examples provided.
list_counterparties List counterparties ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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 | yes | Blockchain: bitcoin, ethereum, bsc or tron. |
| limit | integer | – | Max counterparties to return. |
| with_risk | boolean | – | Attach aml_score/risk_level/sanctioned to each counterparty. |
No output schema declared.
No examples provided.
list_transactions List an address's transfers ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The wallet to list. |
| chain | string | yes | 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. |
No output schema declared.
No examples provided.
screen_address Screen address for AML risk ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The wallet address to screen. |
| chain | string | yes | Blockchain: bitcoin, ethereum, bsc or tron. |
No output schema declared.
No examples provided.
screen_transaction Screen a transaction ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| block_number | integer | – | Optional. Looked up automatically on ethereum and bsc. |
| chain | string | yes | 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 | yes | Transaction hash (0x-prefixed on EVM chains, bare hex txid on bitcoin). |
No output schema declared.
No examples provided.
trace_funds Trace outgoing funds ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address whose outgoing funds to follow. |
| chain | string | yes | 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. |
No output schema declared.
No examples provided.
trace_source_of_funds Trace where funds came from ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The address whose funding to trace. |
| chain | string | yes | Blockchain: bitcoin, ethereum, bsc or tron. |
| max_hops | integer | – | How far back to walk. Default set by the API. |
No output schema declared.
No examples provided.
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.