Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
AML screening for crypto addresses: risk, sanctions, fund tracing and counterparties.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PUBLICAML_API_KEY, PUBLICAML_API_BASEValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"publicaml": {
"command": "npx",
"args": [
"-y",
"@publicaml/mcp-server"
],
"env": {
"PUBLICAML_API_KEY": "your-value",
"PUBLICAML_API_BASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add publicaml --env PUBLICAML_API_KEY=your-value --env PUBLICAML_API_BASE=your-value -- npx -y @publicaml/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"publicaml": {
"command": "npx",
"args": [
"-y",
"@publicaml/mcp-server"
],
"env": {
"PUBLICAML_API_KEY": "your-value",
"PUBLICAML_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"publicaml": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@publicaml/mcp-server"
],
"env": {
"PUBLICAML_API_KEY": "your-value",
"PUBLICAML_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PUBLICAML_API_BASE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account publicaml, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PUBLICAML_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Blockchain AML screening inside Claude Desktop, Cursor, or any other MCP client. Ask about an address in plain language and the assistant checks it against PublicAML: sanctions, issuer freezes, risk propagated through the transaction graph, who funded the wallet and who it dealt with.
Chains: bitcoin, ethereum, bsc, tron. screen_address also covers solana, where the score uses direct evidence only (no risk is propagated), so a Solana address without evidence of its own comes back NOT SCORED rather than 0.
Works without an account. An API key only lifts the rate limit and unlocks forward tracing.
Claude Desktop, claude_desktop_config.json:
{
"mcpServers": { "publicaml": { "command": "npx", "args": ["-y", "@publicaml/mcp-server"] } } }
With an API key:
{
"mcpServers": { "publicaml": { "command": "npx", "args": ["-y", "@publicaml/mcp-server"], "env": { "PUBLICAML_API_KEY": "your-key" } } } }
Cursor uses the same block in .cursor/mcp.json. Claude Code:
claude mcp add publicaml -- npx -y @publicaml/mcp-server
screen_addressRisk level and score, sanctions, Tether/Circle freezes, what the address is (exchange, mixer, gambling, bridge, personal wallet), where its risk comes from, and the incidents it is named in with its role in each (perpetrator, intermediary, recipient, victim, mentioned). Reads POST /v2/enrich.
Victims' reports are kept apart from attribution. A pending claim from a victim report ("this is a KuCoin hot wallet") is printed on its own line, Reported by a victim (not confirmed, does not affect the score): …, with a link to the report, and never as the address's identity. Community incidents that nobody has confirmed are marked community report, not confirmed. A claim a PublicAML curator has confirmed (community:confirmed) is an ordinary attribution.
The answer ends with a link to the public victim-report form with the address prefilled (https://publicaml.org/victim-reports/?chain=…&address=…), so the assistant can offer it to a user who lost funds. The server itself never files reports or writes labels.
chain is optional. Omit it and every chain the address format allows is screened, each result labelled with its chain: the same 0x… string is a different wallet on ethereum, bsc and tron, so it is never guessed silently.
trace_fundsdirection: "incoming" walks the funding backwards to answer "who paid this wallet", stopping at labelled entities rather than walking into an exchange's other customers. direction: "outgoing" follows the largest outgoing flows to where the money left the chain's anonymous part. Outgoing needs an API key.
The walk is bounded by wall clock, so an incomplete answer is returned rather than a timeout, and the answer says which one it is.
list_counterpartiesThree questions, one tool. classify enumerates counterparties and says what each one is (person, venue, hub, deposit address, contract, mint/burn). category answers "did this wallet touch any exchange / mixer / casino". check tests a list of suspect addresses against the wallet.
PARTIAL answer is a floor, not a census.This is evidence for a human decision, not the decision itself.
| Variable | Default | Meaning |
|---|---|---|
PUBLICAML_API_KEY | none | Lifts the anonymous rate limit, unlocks outgoing tracing. |
PUBLICAML_API_BASE | https://intelapi.publicaml.org | API base URL. |
PUBLICAML_TIMEOUT_MS | 60000 | Per-request timeout. |
PUBLICAML_TRACE_CONTINUES | 2 | How many times an incomplete backward walk is resumed automatically. |
The same server is also distributed as an MCPB bundle, which Claude Desktop installs with a double click and no JSON editing. Build it with:
npm run build:mcpb
The bundle lands in dist/. Version, description, licence and the tool list are read from package.json and from the server's own tool definitions, so the bundle cannot drift from the npm release.
npm install
npm test # unit tests, no network node scripts/live.mjs # end-to-end against the live API
version in package.json and both version fields in server.json (the server reads its own version from package.json).npm test, then node scripts/live.mjs.npm publish --access public (npm account of the @publicaml scope).mcp-publisher login github and mcp-publisher publish — updates the MCP Registry entry io.github.publicaml/mcp-server from server.json.npm run build:mcpb and attach dist/publicaml-mcp-server- .mcpb to the GitHub release; tag v .MIT licensed. API docs: https://publicaml.org/api