Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

AgentEconomy Compliance API

REMOTE · API.NETBRAINIS.CO.ZA · SCANNED AUG 3

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

+4 this week 65 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.netbrainis.co.za

# add to Claude Code
claude mcp add --transport http piwe-compliance-api https://api.netbrainis.co.za/mcp
# ~/.codex/config.toml
[mcp_servers.piwe-compliance-api]
url = "https://api.netbrainis.co.za/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "piwe-compliance-api": {
      "type": "remote",
      "url": "https://api.netbrainis.co.za/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add piwe-compliance-api --url https://api.netbrainis.co.za/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  piwe-compliance-api:
    url: "https://api.netbrainis.co.za/mcp"
// mcp.json
{
  "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.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 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 61

    First indexed and scored.

Diagnostics

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 3 Aug 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 6 Jul 2026 4 Oct 2026 ECDSA 256 ECDSA-SHA384 55d69eba47ceb55df04c88d0204ebb40abd
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
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
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
MCP tools — 4 exposed · ~611 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
amountstringTransaction amount
currencystringCurrency code (e.g. USDC, ETH, BTC)
entity_namestringyesFull legal name of the person or entity to screen
transaction_idstringTransaction identifier for audit trail
wallet_addressstringBlockchain 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.

NameTypeReqDescription
countrystringISO 3166-1 alpha-2 country code (e.g. US, GB, ZA, IR)
entity_idstringNational ID, passport number, or company registration number
entity_namestringyesFull legal name of the person or entity to verify
wallet_addressstringBlockchain 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.

NameTypeReqDescription
entity_namestringyesFull legal name of the person or entity
entity_typestringEntity type: 'individual' or 'company'
include_transaction_analysisbooleanInclude on-chain transaction analysis in the report
wallet_addressstringBlockchain 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.

NameTypeReqDescription
wallet_addressstringyesEVM wallet address to screen (0x + 40 hex chars)

No output schema declared.

No examples provided.