C
Limited view
65/100
13 days ago

mpesa-mcp

MCP server for East African fintech APIs — trigger M-Pesa STK Push payments, check transaction status, send SMS to 20+ African networks, and top up airtime via Africa's Talking.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

gabrielmahia

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
23 tools verified — handlers match their declared behaviour
8 read-only tools verified — handlers contain no write/delete/exec
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: MPESA_CONSUMER_KEY, MPESA_CONSUMER_SECRET, AT_API_KEY, MPESA_SECURITY_CREDENTIAL
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMPESA_SANDBOXtrue # set false for production
🔐 secretMPESA_CONSUMER_KEYyour_consumer_key
🔐 secretMPESA_CONSUMER_SECRETyour_consumer_secret
configMPESA_CALLBACK_URL"": "https://yourdomain.com/mpesa/callback",
configMPESA_RESULT_URL
configMPESA_TIMEOUT_URL
configAT_USERNAMEsandbox # your AT username (sandbox for testing)
🔐 secretAT_API_KEYyour_at_api_key
configMPESA_SHORTCODE174379 # sandbox test shortcode
configMPESA_PASSKEYyour_passkey
configMPESA_INITIATOR_NAME
🔐 secretMPESA_SECURITY_CREDENTIAL
configMPESA_OFFICIAL_CONTACT
// quality suggestions

Tool annotations

22/23 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

1/23 tools missing one or more hints — get_model_hint (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

openWorldHint matches behaviour

1 tool claims openWorldHint=false but make outbound HTTP — mpesa_dynamic_qr → dynamic (line 550)

Either flip openWorldHint to true (acknowledging external reach) or refactor the handler to avoid outbound HTTP. If the only network calls are to a known fixed endpoint that you consider part of the tool itself, document that and keep openWorldHint=false; otherwise true is honest.

Tool inputs are validated

22/23 tool handlers declare input schemas (96%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/23 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/gabrielmahia-mpesa-mcp-1uee4e)](https://m8ven.ai/mcp/gabrielmahia-mpesa-mcp-1uee4e)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a7738ea97d0bbc8b89e702978d54e0a77c4f838b
code hash: 2c587231096d767515caaa741657b94d7e65fe2094d33ccff50f9996d5551edf
verified: 8/7/2026, 2:22:37 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client