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

Africa Scam Check

REMOTE · KWEKUANANSI.AI

Fraud patterns a message or call resembles in Kenya and Nigeria, and where to report.

Available components

+3 this week 78 Trust /100

Last scanned (16 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 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 → 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
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 716 tokens (~238/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
What we tested

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 →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +2
    • DNSSEC: fail → pass ▲ security
  • 13 Nov 26 +1
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.07 ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 72

    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 21 Nov 2026 · Probed https://kwekuanansi.ai/mcp/africa-scam-check

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-scam-check Verified 200
http (plaintext) http://kwekuanansi.ai/mcp/africa-scam-check HTTPS enforced 308 https://kwekuanansi.ai/mcp/africa-scam-check
MCP tools · 3 exposed · ~643 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. 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 →

Tool Tokens
africa_scams.check_message ~207

Use this when someone in Kenya or Nigeria shares a text, a WhatsApp message, an email or an account of a phone call about mobile money, a bank, a prize, a job, an investment, a loan or a request for money, and wants to know which known fraud patterns it resembles. It returns the patterns the wording resembles, what the bodies that describe them say to do, and where to report, each with its source. It does not judge the message: say so, and never tell someone a message is fine because nothing matched. Do not use it for other countries, for legal advice, or to decide whether to pay. Leave any PIN, password or one-time code out of what you pass to it.

NameTypeReqDescription
countrystringyesThe country the message or call is about: kenya or nigeria.
messagestringyesThe message as received, or a short account of the call. Leave out any PIN, password or one-time code.
NameTypeReqDescription
countrystringyes–
explore_urlstring––
limitsstringyes–
read_onstringyes–
report_toarrayyes–
resemblesarrayyes–
standing_advicearrayyes–
warning_signsarrayyes–

No examples provided.

africa_scams.list_patterns ~280

Use this when someone asks which frauds the banks, mobile networks and public bodies of Kenya or Nigeria have described, or how a named one works (for example a fake reversal instruction, a one-ring call from abroad, or a message about your BVN). Do not use it for other countries, and do not present the list as complete: it covers patterns that were found described on the bodies' own pages. Do not use it to decide whether a message is fine.

NameTypeReqDescription
countrystringyesThe country the message or call is about: kenya or nigeria.
patternstring–One pattern's id, for its full description. Leave out for the list. Ids for kenya: bank_secret_request, bank_link_sms, sim_swap, cheap_goods_deal, advance_fee_payout, fake_payment_or_overpayment, one…
NameTypeReqDescription
countrystringyes–
explore_urlstring––
limitsstringyes–
patternsarrayyes–
read_onstringyes–
standing_rulesarray––

No examples provided.

africa_scams.where_to_report ~156

Use this when someone in Kenya or Nigeria asks where to report fraud on a phone, a bank account or mobile money, or what the banks and authorities say to do after money or details have gone to a fraudster. It gives the reporting channels the bodies publish and the steps they give, each with its source. Do not use it for other countries or for legal advice, do not suggest that money will be recovered, and leave any PIN, password or one-time code out of what you pass to it.

NameTypeReqDescription
countrystringyesThe country the message or call is about: kenya or nigeria.
money_already_sentboolean–true if money or account details have already gone to the fraudster.
NameTypeReqDescription
countrystringyes–
explore_urlstring––
limitsstringyes–
read_onstringyes–
report_toarrayyes–
stepsarray––

No examples provided.

Install

How do I install the Africa Scam Check MCP server?

Africa Scam Check is a hosted endpoint at https://kwekuanansi.ai/mcp/africa-scam-check, 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

# add to Claude Code
claude mcp add --transport http ai-kwekuanansi-africa-scam-check 'https://kwekuanansi.ai/mcp/africa-scam-check'
Common questions

What is the Africa Scam Check MCP server?

Africa Scam Check is an MCP server listed in the public MCP registry as ai.kwekuanansi/africa-scam-check. Fraud patterns a message or call resembles in Kenya and Nigeria, and where to report. This page covers its hosted endpoint (https://kwekuanansi.ai/mcp/africa-scam-check).

Is the Africa Scam Check MCP server safe to use?

Africa Scam Check scores 78 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 Scam Check MCP server expose?

Africa Scam Check exposes 3 tools: africa_scams.check_message, africa_scams.list_patterns, africa_scams.where_to_report. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.

Does the Africa Scam Check MCP server require authentication?

No. We connected to Africa Scam Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Africa Scam Check MCP server still maintained?

Africa Scam Check 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 Scam Check MCP server?

VerifyMCP ran 13 checks on Africa Scam Check, 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.