Skip to content

AgentEconomy Compliance API MCP server

io.github.Piwe/compliance-apiPiwestreamable-httpv1.0.0Scanned

Paid KYC, AML, and regulatory risk assessment over MCP via x402 USDC micropayments on Base.

4 tools: 4 can delete or cancel things.

Tools: 4 delete, 0 irreversible, 0 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AgentEconomy Compliance API MCP server can do

The AgentEconomy Compliance API MCP server is published by the GitHub account Piwe. It has 4 tools. It can delete or cancel things (4 tools: aml_screen, kyc_check, risk_report and wallet_screen). None of its tools only reads.

4 tools bring in text other people can write (aml_screen, kyc_check, risk_report and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 4Claude Code: deny
  • aml_screenScreen an entity against Anti-Money Laundering (AML) watchlists including OFAC SDN and UN sanctions.Reads text others writeNo findings

    Why it is in this group

    • The input carries an amount (input.amount) and a currency, so it moves money.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Screen an entity against Anti-Money Laundering (AML) watchlists including OFAC SDN and UN sanctions. Returns risk level, risk score, recommendation (approve/review/reject), and sanctions match details. Uses Jaro-Winkler fuzzy name matching for accurate detection. Cost: $0.05 USDC per screening. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • kyc_checkRun a KYC (Know Your Customer) identity verification check against OFAC and UN sanctions lists.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Run a KYC (Know Your Customer) identity verification check against OFAC and UN sanctions lists. Returns verification status, risk score (0-100), and sanctions/PEP match results. Powered by real government sanctions data (OFAC SDN + UN Security Council). Cost: $0.01 USDC per check. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • risk_reportGenerate a comprehensive regulatory risk assessment report combining KYC verification, AML sanctions screening, and multi-jurisdiction risk analysis.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Generate a comprehensive regulatory risk assessment report combining KYC verification, AML sanctions screening, and multi-jurisdiction risk analysis. Returns overall risk level, risk score, sanctions results, jurisdiction-specific risk factors, and recommended compliance actions. Cost: $0.10 USDC per report. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • wallet_screenScreen a blockchain wallet address for compliance risk.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Screen a blockchain wallet address for compliance risk. Combines a direct OFAC sanctioned-address check with on-chain exposure analysis across Ethereum and Base — flagging sanctioned counterparties the wallet transacted with and known mixer (e.g. Tornado Cash) exposure. Returns risk level, score (0-100), and recommendation (approve/review/reject). No entity name required. Cost: $0.05 USDC per screening. Caller must supply a signed X-PAYMENT header on the MCP HTTP request.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:00 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 destructive). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.netbrainis.co.za/mcp: tools/list returned 4 tools to an anonymous client, including aml_screen (destructive), kyc_check (destructive), risk_report (destructive), wallet_screen (destructive)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http compliance-api https://api.netbrainis.co.za/mcp
claude mcp add --transport http compliance-api https://api.netbrainis.co.za/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [],
    "deny": [
      "mcp__compliance-api__aml_screen",
      "mcp__compliance-api__kyc_check",
      "mcp__compliance-api__risk_report",
      "mcp__compliance-api__wallet_screen"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as compliance-api. Review it before you use it.

Capability tags behind 4 rules
  • mcp__compliance-api__aml_screen untrusted-input
  • mcp__compliance-api__kyc_check untrusted-input
  • mcp__compliance-api__risk_report untrusted-input
  • mcp__compliance-api__wallet_screen untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Piwe/compliance-api/verify?hash=1e9a0e46f87f64c1abebe9d0a97891d6530b64be304f411e4c010d1da753b4b3" | jq -e '.changed == false'

Pinned hash 1e9a0e46f87f, from Nov 16, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Piwe/compliance-api/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Piwe/compliance-api
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Piwe/compliance-api.svg)](https://radar.anlyon.com/servers/io.github.Piwe/compliance-api)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.

AgentEconomy Compliance API MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AgentEconomy Compliance API MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AgentEconomy Compliance API MCP server delete data?

Yes. 4 tools can delete, cancel or revoke something: aml_screen, kyc_check, risk_report and wallet_screen.

Can the AgentEconomy Compliance API MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AgentEconomy Compliance API MCP server have?

4 tools: 4 destructive. aml_screen, kyc_check, risk_report and wallet_screen.

Does the AgentEconomy Compliance API MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AgentEconomy Compliance API MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AgentEconomy Compliance API MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.