Home / MCP registry index / io.github.nyuchi/mukoko-news
Mukoko News
io.github.nyuchi/mukoko-news in the official MCP registry.
Endpoint https://news.mukoko.dev/mcp. Source: github.com/nyuchi/mukoko-news.
The registry describes it as: Pan-African news & analytics for Zimbabwe and 15 African countries: briefings and trends.
We read its 16 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_briefing track_story get_location_news compare_locations get_source_view find_stories get_article list_categories list_sources get_stats get_my_feed get_trending_analytics detect_surge get_content_analytics trigger_enrichment drain_enrichment_backlog
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-nyuchi-mukoko-news)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.