GoodTurnStudioVerified
Shariah screening of US stocks under four standards, halal alternatives, purification and zakat.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 38 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Free crypto AML/KYT screening for BTC/ETH/BSC/TRON — risk score, sanctions, source of funds.
0 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using io.github.saloprj/publicaml
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http io-github-saloprj-publicaml https://mcp.publicaml.org/mcpCapabilities
Explain WHERE an address's AML risk comes from: for each risk source (sanctioned entity, hack, mixer, scam, frozen funds) the chain of wallets the money took from that source to this address, hop by hop, with the label of each wallet, the amounts and assets on each link, dates and transaction hashes. Use it when the user asks why an address is risky, where its risk or dirty money came from, or through whom the funds arrived. Read-only.
DiscoveredFor 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.
DiscoveredList 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.
DiscoveredA 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.
DiscoveredScreen a crypto wallet address for AML/KYT risk. Returns an AML score (0-100), risk_level (LOW/MEDIUM/HIGH/CRITICAL), what the address is (axes: business, legal_status, asset_control, ...), sanctioned exposure, source-of-funds and the incidents (hacks, scams, reports) the address appears in, with its role in each. Chains: bitcoin, ethereum, bsc, tron, solana (on solana the score uses the address's own evidence only). aml_score null means not assessed, never 0 or clean. Anything under community_claims is one victim's unconfirmed report: quote it as a report, never as who the address is. An incident marked 'community report, not confirmed' accuses nobody; 'victim, not accused' is the opposite of an accusation. report_url is the victim-report form: offer it only if the user lost funds. Read-only: it only looks the address up, it never changes anything.
DiscoveredScreen 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.
DiscoveredFollow 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.
DiscoveredWalk 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. Answers source-of-funds questions. Read-only: it only reads on-chain history.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 188 ms | 8 |