Afriset Fintech

The Afriset MCP server

The register is MCP-first: your compliance, ops and engineering tools (Claude, Cursor, ChatGPT, or any MCP client) can query it directly. Remote, authless, read-only. Every response carries the official source, the as-of date, and a source-currency signal.

Endpoint

https://mcp.afriset.com/mcp   (streamable HTTP)

Claude (web/desktop): Settings → Connectors → Add custom connector → paste the URL. Claude Code: claude mcp add --transport http afriset https://mcp.afriset.com/mcp

Tools

list_licensed(activity, jurisdiction?)

Who holds the licence for a canonical activity, per the official register — with each provider's local licence category, status as reported, and provenance. 

{"activity": "EMONEY_ISSUE", "jurisdiction": "Ghana"}

map_license(activity, from, to)

The cross-country normalization: which local licence category is the equivalent in another market ("a Nigerian MMO ≈ a Ghanaian DEMI ≈ a Kenyan E-Money Issuer"). 

{"activity": "REMITTANCE_XBORDER", "from": "NG", "to": "ZA"}

Coverage

Activities: fintech:EMONEY_ISSUE · fintech:PAYMENT_PROCESSING · fintech:REMITTANCE_XBORDER · fintech:SWITCHING. Jurisdictions: GH (Ghana) · KE (Kenya) · NG (Nigeria) · RW (Rwanda) · TZ (Tanzania) · UG (Uganda) · ZA (South Africa) · ZM (Zambia). Coverage per slice, including honest gaps (registers a regulator hasn't published or we couldn't fetch), is reported in every response and on the register pages.

Notes