whatsapp-monitoring (nkarkare/whatsapp-monitoring) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 6 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
12 days ago

whatsapp-monitoring

→ nkarkare/whatsapp-monitoring· listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

nkarkare

Source: github_code

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: CLAUDE_API_KEY, ERPNEXT_API_KEY, ERPNEXT_API_SECRET
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.
configADMIN_WHATSAPP_NUMBER
configDEFAULT_TASK_ASSIGNEE
configERPNEXT_URL
configAI_TASK_DETECTION_ENABLED
🔐 secretCLAUDE_API_KEY
configCLAUDE_API_URL
configCLAUDE_MODEL
configAI_CONFIDENCE_THRESHOLD
configAI_MIN_MESSAGE_LENGTH
configAI_BATCH_ANALYSIS
configAI_BATCH_SIZE
configAI_DAILY_BUDGET
configAI_LEARNING_ENABLED
configAI_LEARNING_DB_PATH
configMESSAGES_DB_PATHMonitor not finding the database: Check that the in your config points to the correct WhatsApp Bridge SQLite database
configWHATSAPP_API_URL
configDAILY_SUMMARY_ENABLED
configDAILY_SUMMARY_RECIPIENT
configDAILY_SUMMARY_GROUPS
configDAILY_SUMMARY_TIME
configDAILY_SUMMARY_TIMEZONE
configKEYWORD_MONITORING_ENABLED
configKEYWORD_ALERT_RECIPIENT
configMONITORED_KEYWORDS
configMONITORED_GROUPS
configKEYWORD_ALERT_COOLDOWN
🔐 secretERPNEXT_API_KEY
🔐 secretERPNEXT_API_SECRET
configFUZZY_MATCH_THRESHOLD
configMAX_USER_SUGGESTIONS
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

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

All four hints declared on every tool

6/6 tools missing one or more hints — create_erp_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_erp_users (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_users (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Secrets not logged

1 secret value sent to logger.info

Redact or omit secret values from log output.

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 4 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/nkarkare/whatsapp-monitoring)](https://m8ven.ai/mcp/nkarkare/whatsapp-monitoring)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d0f57bd42fa6c2a48ccac253139c941b2835c615
code hash: 38620277c6cc6cb41ffbd0c3525e93a3f8df1e38a8c1bf8f0725cb0bdb4ef482
verified: 9/1/2026, 5:45:54 PM
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