@theyahia/africas-talking-mcp
npm
v1.0.1
Published by @theyahia — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Untrusted-input tools ([get_delivery_report]) co-exist with external-action tools ([send_sms, send_bulk_sms]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [get_delivery_report] → sinks [send_sms, send_bulk_sms]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow get_delivery_report → send_sms
Each tool and what it can reach — statically extracted from the published source.
get_delivery_reportingests untrusted inputsend_bulk_smsnetwork egresssend_smsnetwork egresscreate_ussdno sensitive capabilityget_balanceno sensitive capabilitymake_callno sensitive capabilitymobile_checkoutno sensitive capabilitysend_airtimeno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.1 latest |
A 96/100 | 1 | 1.8.0 | 2026-07-23 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @theyahia/africas-talking-mcp --online
Security scan results for the 21e14 MCP server.
Security scan results for the Agentgate Ucp MCP server.
Security scan results for the Autotask MCP server.
Security scan results for the B2c Dx MCP server.
Security scan results for the Brreg MCP server.
Security scan results for the Canlii MCP server.