Africa Contacts
REMOTE · KWEKUANANSI.AI
Customer-care and complaints numbers in Kenya and Nigeria, each read on the body's own website.
Available components
Last scanned (20 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 648 tokens (~216/item across 3 items; 3 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 Management33
- Stability observed for 10 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 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.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- DNSSEC: fail → pass ▲ security
- 13 Nov 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.
- 12 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 73
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 21 Nov 2026 · Probed https://kwekuanansi.ai/mcp/africa-contacts
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kwekuanansi.ai | CN=YR1,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | RSA 2048 | SHA256-RSA | 5a9703a2d747be131c28ec7c7c14426de31 |
| SANs: kwekuanansi.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of kwekuanansi.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| kwekuanansi.ai. | DS published | 2371 | 13 | Verified |
| kwekuanansi.ai. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data: https://fal.media https://*.fal.media; media-src 'self' data: blob:; font-src 'self' data:; style-src 'self'; script-src 'self'; connect-src 'self' https://anansi.cashplanet.io https://fal.media https://*.fal.media; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kwekuanansi.ai/mcp/africa-contacts | Verified | 200 | |
| http (plaintext) | http://kwekuanansi.ai/mcp/africa-contacts | HTTPS enforced | 308 | https://kwekuanansi.ai/mcp/africa-contacts |
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 →
africa_contacts.check_number Check who publishes a phone number in Kenya or Nigeria ~205
Use this when someone was given a phone number said to belong to a bank, mobile network or public office in Kenya and Nigeria and asks whether it is really theirs (for example "is 0711 087 000 really KCB" or "a caller from 0722 000 000 says he is Safaricom"). It says which organisation on its list publishes that number on its own website, or that none does. A number that is not found may still be genuine, and the tool says so. Do not use it to look up who owns a private number, to trace a caller, or for numbers outside Kenya and Nigeria.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | The country the organisation is in: kenya or nigeria. |
| number | string | yes | The phone number or short code as given, for example "0711 087 000", "+254 722 000 000", "+234 906 980 3800" or "100". |
| Name | Type | Req | Description |
|---|---|---|---|
| caution | string | yes | – |
| country | string | yes | – |
| explore_url | string | – | – |
| found | boolean | yes | – |
| number | string | yes | – |
| published_by | array | yes | – |
| read_on | string | yes | – |
No examples provided.
africa_contacts.find Contact numbers of an organisation in Kenya or Nigeria ~234
Use this when someone asks for the customer-care, complaints or emergency number of a bank, mobile network, electricity company, payments company, regulator or public office in Kenya and Nigeria (for example "what is the KCB customer care number", "how do I reach Safaricom about M-PESA fraud" or "Access Bank contact centre"). It returns numbers read on the organisation's own website, with the page and the date. Give those numbers rather than one from memory or from a web search. Where the organisation's own site could not be read, it says so and gives no number. Do not use it for a shop, a school, a hospital, a person, or an organisation outside Kenya and Nigeria: it covers a fixed list and says when a name is not on it.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | The country the organisation is in: kenya or nigeria. |
| organisation | string | yes | The organisation's name or usual short name, for example "KCB", "Safaricom", "Kenya Power", "KRA", "Access Bank", "MTN" or "JAMB". |
| Name | Type | Req | Description |
|---|---|---|---|
| caution | string | yes | – |
| country | string | yes | – |
| explore_url | string | – | – |
| not_published | array | – | – |
| organisations | array | yes | – |
| read_on | string | yes | – |
No examples provided.
africa_contacts.list Organisations in Kenya or Nigeria whose contacts are listed ~121
Use this when someone asks which organisations in Kenya and Nigeria this tool has numbers for, which it looked for and could not read, or wants one group all at once (the emergency lines, or the places to report fraud and make complaints). Do not use it when one organisation is named: use africa_contacts.find.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | The country the organisation is in: kenya or nigeria. |
| kind | string | – | One group: emergency, regulator, network, bank, payments, utility, public_service. Leave out for the names of all. |
| Name | Type | Req | Description |
|---|---|---|---|
| caution | string | yes | – |
| country | string | yes | – |
| explore_url | string | – | – |
| groups | array | yes | – |
| not_published | array | – | – |
| organisations | array | – | – |
| read_on | string | yes | – |
No examples provided.
How do I install the Africa Contacts MCP server?
Africa Contacts is a hosted endpoint at https://kwekuanansi.ai/mcp/africa-contacts, 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 · kwekuanansi.ai
claude mcp add --transport http ai-kwekuanansi-africa-contacts 'https://kwekuanansi.ai/mcp/africa-contacts'
What is the Africa Contacts MCP server?
Africa Contacts is an MCP server listed in the public MCP registry as ai.kwekuanansi/africa-contacts. Customer-care and complaints numbers in Kenya and Nigeria, each read on the body's own website. This page covers its hosted endpoint (https://kwekuanansi.ai/mcp/africa-contacts).
Is the Africa Contacts MCP server safe to use?
Africa Contacts scores 79 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 Africa Contacts MCP server expose?
Africa Contacts exposes 3 tools: africa_contacts.find, africa_contacts.check_number, africa_contacts.list. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.
Does the Africa Contacts MCP server require authentication?
No. We connected to Africa Contacts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Africa Contacts MCP server still maintained?
Africa Contacts is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Africa Contacts MCP server?
VerifyMCP ran 13 checks on Africa Contacts, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.