io.github.gabrielmahia/wapimaji-mcp
PYPI · WAPIMAJI-MCP
Kenya drought-response toolkit: simulated drought phases, confirmed SMS alerts, coordination events
Available components
Last scanned (1 day ago)
Scores higher than 95% of PyPI servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 25 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to gabrielmahia/wapimaji-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 626 tokens (~156/item across 4 items; 4 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 Management70
- Stability observed for 21 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.16 → 0.1.17 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 +1
- Package version: 0.1.15 → 0.1.16 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Package version: 0.1.14 → 0.1.15 functional
- 22 Oct 26 +11
- Provenance: unverified → pass ▲ security
- The attested source repository moved: gabrielmahia/wapimaji-mcp security
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 4 Nov 2026 · Analysed pypi/wapimaji-mcp@0.1.17
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | gabrielmahia/wapimaji-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/gabrielmahia/wapimaji-mcp/.github/workflows/publish.yml@refs/tags/v0.1.17 |
| Rekor log index | 3646551658 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f117eee175748a174ab6f0833c280a40789c9e3839e34f1263638d8e98928189 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 25 packages
| Packages resolved | 25 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_drought_alerts Get Drought Alerts ~139
List SIMULATED county drought alerts at or above a minimum phase (1 minimal, 2 stressed, 3 crisis, 4 emergency, 5 famine; default 3). Use only to build and test flows: this is sandbox data, not NDMA observation, and production returns an explicit not-implemented error. Returns the counties at that phase with population affected, the count, the phase queried and its label, sandbox true and the source. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| min_phase | integer | – | Minimum phase: 1 minimal, 2 stressed, 3 crisis, 4 emergency, 5 famine (default 3). |
Structured output declared, but exposes no named fields.
No examples provided.
get_drought_status Get Drought Status ~130
SIMULATED drought phase for a Kenyan county: the values are generated from the county name, are NOT NDMA data and not an observation, and every answer says synthetic true. Use only to build and test flows, never for decisions. An unknown county returns an error; in live mode it returns an explicit not-implemented error because no data source is integrated. Returns county, phase, phase label, rainfall deficit percent, population affected, synthetic true, the source and a note. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | yes | Kenyan county name such as Turkana, Marsabit or Garissa. |
Structured output declared, but exposes no named fields.
No examples provided.
publish_drought_coordination Publish Drought Coordination ~175
Publish a drought coordination event to africa-coord-bus so other servers can react (insurance evaluation, advisories, malnutrition watch, county alerts). Use when coordinating a drought response across servers. Phases 2 stressed, 3 crisis and 4 emergency trigger coordination; phase 0 takes the phase and deficit from get_drought_status, which is SIMULATED data. Returns published false with a reason if africa-coord-bus is not installed. Side effect: emits an event to the bus.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | yes | Kenyan county name. |
| phase | integer | – | Drought phase 1-5; 0 (default) takes it from get_drought_status. |
| rainfall_deficit_pct | number | – | Rainfall deficit in percent; used when phase is given (default 0). |
Structured output declared, but exposes no named fields.
No examples provided.
sms_drought_alert Sms Drought Alert ~182
Send a drought alert SMS through Africa's Talking. Use only when the user has explicitly approved this exact message and recipient list. SENDS TO REAL PEOPLE: real messages go out only when SANDBOX=false and confirm_send=true; otherwise it simulates and reports the recipient count without contacting the provider. Returns sent, count and the provider response, or an error. Messages are limited to 160 characters. Sending cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_send | boolean | – | Set true only after the user explicitly approves this exact send; required for live sending. |
| message | string | yes | SMS text, at most 160 characters. |
| phone_numbers | array | yes | List of recipient numbers in E.164 format such as ['+254712345678']. |
| sender_id | string | – | Registered Africa's Talking sender ID (default WAPIMAJI). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.gabrielmahia/wapimaji-mcp server?
io.github.gabrielmahia/wapimaji-mcp runs locally as a PyPI package, launched with uvx wapimaji-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · wapimaji-mcp
claude mcp add gabrielmahia-wapimaji-mcp -- uvx wapimaji-mcp
What is the io.github.gabrielmahia/wapimaji-mcp server?
io.github.gabrielmahia/wapimaji-mcp is listed in the public MCP registry as io.github.gabrielmahia/wapimaji-mcp. Kenya drought-response toolkit: simulated drought phases, confirmed SMS alerts, coordination events. This page covers its PyPI package (wapimaji-mcp).
Is the io.github.gabrielmahia/wapimaji-mcp server safe to use?
io.github.gabrielmahia/wapimaji-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 io.github.gabrielmahia/wapimaji-mcp server expose?
io.github.gabrielmahia/wapimaji-mcp exposes 4 tools: get_drought_status, get_drought_alerts, sms_drought_alert, publish_drought_coordination. Their descriptions and schemas cost roughly 626 tokens of context every time the server is loaded.
Is the io.github.gabrielmahia/wapimaji-mcp server still maintained?
io.github.gabrielmahia/wapimaji-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.gabrielmahia/wapimaji-mcp server under?
io.github.gabrielmahia/wapimaji-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.