Skip to content
External endpointresponds

Mukoko News

Pan-African news & analytics for Zimbabwe and 15 African countries: briefings and trends.

Endpoint URL
https://news.mukoko.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
3,089 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.nyuchi/mukoko-news

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
mukoko-news
Version
3.1.0
Capability keys
tools, resources
Tool names
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
Instructions excerpt

You are connected to Mukoko News, a Pan-African news platform covering Zimbabwe and 15 other African countries. All data comes from MongoDB Atlas. Tools are task-oriented: get_briefing for "what's happening in X", track_story for developing stories, get_location_news for place-specific news, compare_locations for side-by-side country comparison, get_source_view for a publication's perspective. List tools return excerpts only; get_article returns the full article body inline as markdown (truncated at ~8000 characters with a link to continue in the Mukoko app). Open data analytics: get_trending_analytics (trending topics), detect_surge (sudden coverage spikes vs 7-day baseline), get_content_analytics (category/country breakdown). Personalised: get_my_feed requires a WorkOS bearer token. All tools understand country codes (ZW, KE, NG), country names, region names (East Africa, Southern Africa, West Africa, North Africa), and major city names.

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 3,400ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 3,345ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 2,994ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 3,089ms