mansa-african-identity
Registry code: fa69eb4e96e72b12
African bank & SWIFT codes, NUBAN resolution, mobile networks, holidays and ISO 4217 currencies.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mansaapi.com/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is mansa-african-identity live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is mansa-african-identity free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does mansa-african-identity have?
- 6 tools: get_public_holidays, list_banks, lookup_phone_network, get_currency, lookup_bank, resolve_nuban.
- Is mansa-african-identity safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- look up african bank and swift codes
- resolve a nigerian nuban account
- identify mobile network of a phone number
- get public holidays for a country
- takes → gives
- text → data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_public_holidays reads unknown 5h ago
Return the public holidays for a country and calendar year, with each holiday's date, name and type. Names are returned in English wherever the country publishes it; pass a language code for others (Kenya also publishes Swahili).
{ "type": "object", "required": [ "country", "year" ], "properties": { "lang": { "type": "string", "description": "Optional language code for holiday names, e.g. 'sw' for Swahili." }, "year": { "type": "number", "description": "Four-digit calendar year, e.g. 2026." }, "country": { "type": "string", "description": "ISO-2 country code, e.g. NG, KE, GH, ZA." } } }arguments 21 lineslist_banks reads unknown 5h ago
List every bank and financial institution held for a country, with its bank code, SWIFT/BIC, USSD shortcode and mobile-money flag. Use this to build a bank picker or to reconcile a list of institutions.
{ "type": "object", "required": [ "country" ], "properties": { "country": { "type": "string", "description": "ISO-2 country code, e.g. NG, GH, KE, ZA, EG, MA, ZM, TZ." }, "mobile_money_only": { "type": "boolean", "description": "Return only mobile-money providers (default false)." } } }arguments 16 lineslookup_phone_network reads unknown 16h ago
Resolve an African phone number to its mobile network operator from the number's prefix. Accepts local or international format. Useful for routing a mobile-money payout to the right provider or validating a number before sending an OTP.
{ "type": "object", "required": [ "phone" ], "properties": { "phone": { "type": "string", "description": "Phone number, local (08031234567) or international (+2348031234567)." } } }arguments 12 linesget_currency reads unknown 16h ago
Return the ISO 4217 record for a currency: its code, name, symbol, how many decimal places it uses, and every country that uses it.
{ "type": "object", "required": [ "code" ], "properties": { "code": { "type": "string", "description": "ISO 4217 currency code, e.g. NGN, KES, XAF, ZAR." } } }arguments 12 lineslookup_bank reads unknown 16h ago
Identify an African bank from any identifier you hold: its name, domestic sort/bank code, SWIFT/BIC code, or USSD shortcode. Works as a reverse lookup, so pass a bare SWIFT code like 'NLCBTZTX' to find out which institution it belongs to. Returns the bank's name, country, type, bank code, SWIFT/BIC, USSD shortcode and whether it supports mobile money.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "number", "description": "Max results (default 10, max 50)." }, "query": { "type": "string", "description": "Bank name, bank/sort code, SWIFT/BIC code, or USSD shortcode." }, "country": { "type": "string", "description": "Optional ISO-2 country code to scope the search (e.g. NG, GH, KE, ZA, TZ)." } } }arguments 20 linesresolve_nuban reads unknown never probed
Work out which Nigerian banks a 10-digit NUBAN account number could belong to. The CBN check digit is computed from the bank code plus the first nine digits, so testing the number against every bank code narrows a shortlist without contacting any bank. Typically reduces ~30 banks to ~3. This confirms checksum validity only: it does NOT confirm the account exists, and it never returns the account holder's name, which requires a licensed NIBSS account-name enquiry.
{ "type": "object", "required": [ "account" ], "properties": { "account": { "type": "string", "description": "The 10-digit Nigerian account number." }, "bank_code": { "type": "string", "description": "Optional. If given, validate against just this bank code instead of scanning all." } } }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idfa69eb4e96e72b12.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fa69eb4e96e72b12/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fa69eb4e96e72b12?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.