Skip to main content
Glama
publicaml

PublicAML MCP Server

Official
by publicaml
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PUBLICAML_API_KEYNoLifts the anonymous rate limit and unlocks outgoing tracing.none
PUBLICAML_API_BASENoAPI base URL.https://intelapi.publicaml.org
PUBLICAML_TIMEOUT_MSNoPer-request timeout in milliseconds.60000
PUBLICAML_TRACE_CONTINUESNoHow many times an incomplete backward walk is resumed automatically.2

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
screen_addressA

AML screening for one blockchain address: risk level and score, sanctions, issuer freezes (Tether/Circle), what the address is (exchange, mixer, gambling, bridge, personal wallet) and where its risk comes from. Chains: bitcoin, ethereum, bsc, tron.

Read the answer this way: sanctioned: true is a blocking fact on its own, independent of the score. The score is a risk reading 0-100, never a share of the funds. An address absent from the data is reported as NOT FOUND and must not be presented as clean.

Chain is part of the address's identity, not a hint: the same 0x address is a different wallet on ethereum, bsc and tron. Pass chain when you know it; if you omit it, every chain the format allows is screened and each result is labelled with its chain.

trace_fundsA

Follows the money one direction at a time.

incoming walks funding backwards: who paid this wallet. The trail stops at labelled entities (it reports the exchange rather than walking into its other customers) and at unlabelled addresses whose degree makes them a service.

outgoing follows the largest outgoing flows forward to where the money left the anonymous part of the chain (exchange, OTC, mixer) and what is still sitting in unlabelled dead ends. Outgoing tracing needs an API key.

This is a lead-generating tool, not exhaustive accounting: the walk is bounded by wall clock, so a partial answer is returned rather than a timeout, and 'nothing found' can mean 'the budget ran out'. The answer says which one it was; report that honestly.

list_counterpartiesA

Who a wallet dealt with and for how much, in one of three modes:

classify — enumerate the counterparties and say what each one IS: a person, a venue (exchange/service), a hub, a deposit address, a contract or a mint/burn pseudo-address. This is the mode for 'which ordinary people funded this wallet'. An unlabelled counterparty is NOT thereby a person; that is what this mode's degree probe decides. category — did this wallet touch any exchange / mixer / gambling site / bridge at all. check — you already have suspect addresses and want to know whether this wallet dealt with them, and for how much. Addresses with no recorded interaction are simply absent from the answer.

The list is ranked and capped, so a partial answer is a floor, not the complete set, and a degree figure is a lower bound measured in a window.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation4/5

Each tool targets a different AML task (address screening, fund tracing, counterparty listing), but trace_funds (incoming) and list_counterparties (classify/category) both surface who a wallet interacted with, creating some boundary blur. Descriptions clarify scope, so misselection is unlikely but possible.

Naming Consistency5/5

All three names follow a consistent snake_case verb_noun pattern (screen_address, trace_funds, list_counterparties). No deviations, making the set predictable and easy to scan.

Tool Count5/5

Three tools is well-scoped for a focused AML API, and each tool encapsulates a distinct, multi-purpose operation (screening, tracing, counterparty analysis). No tool feels redundant or missing.

Completeness4/5

Covers core AML workflows: risk/sanctions screening, fund tracing, and counterparty classification. Minor gaps exist, such as batch address screening or granular transaction-level retrieval, but agents can work around them for most use cases.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources