AgentEconomy Compliance API
REMOTE · API.NETBRAINIS.CO.ZA · SCANNED SEP 20
Paid KYC, AML, and regulatory risk assessment over MCP via x402 USDC micropayments on Base.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (aml_screen). See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 801 tokens (~200/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 AgentEconomy Compliance API MCP server?
AgentEconomy Compliance API is a hosted endpoint at https://api.netbrainis.co.za/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 · api.netbrainis.co.za
claude mcp add --transport http piwe-compliance-api 'https://api.netbrainis.co.za/mcp'
{
"mcpServers": {
"piwe-compliance-api": {
"url": "https://api.netbrainis.co.za/mcp"
}
}
} {
"servers": {
"piwe-compliance-api": {
"type": "http",
"url": "https://api.netbrainis.co.za/mcp"
}
}
} [mcp_servers.piwe-compliance-api] url = "https://api.netbrainis.co.za/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"piwe-compliance-api": {
"type": "remote",
"url": "https://api.netbrainis.co.za/mcp",
"enabled": true
}
}
} openclaw mcp add piwe-compliance-api --url 'https://api.netbrainis.co.za/mcp' --transport streamable-http
mcp_servers:
piwe-compliance-api:
url: "https://api.netbrainis.co.za/mcp" {
"McpServers": {
"piwe-compliance-api": {
"Transport": "http",
"Url": "https://api.netbrainis.co.za/mcp"
}
}
} assistant mcp add piwe-compliance-api -t streamable-http -u 'https://api.netbrainis.co.za/mcp'
{
"mcpServers": {
"piwe-compliance-api": {
"type": "http",
"url": "https://api.netbrainis.co.za/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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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://api.netbrainis.co.za/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.netbrainis.co.za | CN=YE1,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 55366ad5eba8dd910fe7220bf33cd04ce75 |
| SANs: api.netbrainis.co.za | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.netbrainis.co.za. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| za. | present | 45749 | 8 | Verified |
| co.za. | present | 41369 | 8 | Verified |
| netbrainis.co.za. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.netbrainis.co.za/mcp | Verified | 200 | |
| http (plaintext) | http://api.netbrainis.co.za/mcp | HTTPS enforced | 308 | https://api.netbrainis.co.za/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 →
aml_screen ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | Transaction amount |
| currency | string | – | Currency code (e.g. USDC, ETH, BTC) |
| entity_name | string | yes | Full legal name of the person or entity to screen |
| transaction_id | string | – | Transaction identifier for audit trail |
| wallet_address | string | – | Blockchain wallet address to check |
No output schema declared.
No examples provided.
kyc_check ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. US, GB, ZA, IR) |
| entity_id | string | – | National ID, passport number, or company registration number |
| entity_name | string | yes | Full legal name of the person or entity to verify |
| wallet_address | string | – | Blockchain wallet address (e.g. 0x...) |
No output schema declared.
No examples provided.
risk_report ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_name | string | yes | Full legal name of the person or entity |
| entity_type | string | – | Entity type: 'individual' or 'company' |
| include_transaction_analysis | boolean | – | Include on-chain transaction analysis in the report |
| wallet_address | string | – | Blockchain wallet address |
No output schema declared.
No examples provided.
wallet_screen ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_address | string | yes | EVM wallet address to screen (0x + 40 hex chars) |
No output schema declared.
No examples provided.
What is the AgentEconomy Compliance API MCP server?
AgentEconomy Compliance API is an MCP server listed in the public MCP registry as io.github.Piwe/compliance-api. Paid KYC, AML, and regulatory risk assessment over MCP via x402 USDC micropayments on Base. This page covers its hosted endpoint (https://api.netbrainis.co.za/mcp).
Is the AgentEconomy Compliance API MCP server safe to use?
AgentEconomy Compliance API scores 76 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 AgentEconomy Compliance API MCP server expose?
AgentEconomy Compliance API exposes 4 tools: aml_screen, kyc_check, risk_report, wallet_screen. Their descriptions and schemas cost roughly 611 tokens of context every time the server is loaded.
Does the AgentEconomy Compliance API MCP server require authentication?
No. We connected to AgentEconomy Compliance API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentEconomy Compliance API MCP server still maintained?
AgentEconomy Compliance API 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.