# Mukoko News (remote · news.mukoko.dev)

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

- Trust score: 59/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `news.mukoko.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/nyuchi-mukoko-news/news.md), [page](https://verifymcp.io/servers/nyuchi-mukoko-news/news)
- npm · `@nyuchi/mukoko-news-mcp`: 39/100, [markdown](https://verifymcp.io/servers/nyuchi-mukoko-news/nyuchi-mukoko-news-mcp.md), [page](https://verifymcp.io/servers/nyuchi-mukoko-news/nyuchi-mukoko-news-mcp)

## Channel facts

- Endpoint: `https://news.mukoko.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1490 tokens (~93/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http nyuchi-mukoko-news https://news.mukoko.dev/mcp
```

### Codex

```toml
[mcp_servers.nyuchi-mukoko-news]
url = "https://news.mukoko.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nyuchi-mukoko-news": {
      "type": "remote",
      "url": "https://news.mukoko.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nyuchi-mukoko-news --url https://news.mukoko.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nyuchi-mukoko-news:
    url: "https://news.mukoko.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "nyuchi-mukoko-news": {
      "type": "http",
      "url": "https://news.mukoko.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 57, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (16)

### `get_briefing` (~132 tokens)

Answer "What's happening in [place/topic]?" — top story, recent articles, and trending topics in one call. Accepts country codes (ZW, KE), region names (East Africa, Southern Africa), category topics (politics, business), or omit focus for a pan-African overview. Returns short excerpts with word counts and app links only — call get_article with an article id to read a full article body inline.

Input parameters:

- `focus` (string): Country code, region, category, or topic (optional)
- `limit` (number): Max articles, 1–12 (default 8)

### `track_story` (~102 tokens)

Follow the development of a news story over time. Returns articles in chronological order showing how a story evolved. Use since to control the lookback window.

Input parameters:

- `country` (string): Limit to a country code (optional)
- `limit` (number): Max articles, 1–20 (default 10)
- `since` (string): Lookback window (default: week)
- `topic` (string, required): Topic, keyword, event, or person name to track

### `get_location_news` (~79 tokens)

News from a specific place in Africa. Accepts country codes, country names, region names, or city names.

Input parameters:

- `category` (string): Category to filter (optional)
- `limit` (number): Max articles, 1–20 (default 10)
- `location` (string, required): Country code, country name, region, or city

### `compare_locations` (~78 tokens)

Compare news coverage between 2–4 African countries or regions side by side.

Input parameters:

- `limit` (number): Max articles per location, 1–10 (default 5)
- `locations` (array, required): 2–4 country codes, country names, or region names
- `topic` (string): Narrow comparison to a topic (optional)

### `get_source_view` (~63 tokens)

See how a specific news source is covering a topic.

Input parameters:

- `limit` (number): Max articles, 1–20 (default 8)
- `source` (string, required): Publication name (partial match)
- `topic` (string): Topic to filter by (optional)

### `find_stories` (~115 tokens)

Search articles by keyword, tag, category, or country. Results carry short excerpts, word counts, and app links only — call get_article with a result's id to read the full article body inline.

Input parameters:

- `category` (string): Category slug or name (optional)
- `country` (string): Country code (optional)
- `limit` (number): Max results, 1–20 (default 10)
- `q` (string): Keyword or phrase (optional)
- `tag` (string): Tag name (optional)

### `get_article` (~91 tokens)

Read a single article by ID or slug. Returns the full article body inline as markdown (truncated at ~8000 characters with a link to continue in the app) plus source metadata and the Mukoko app URL. Use this after a list tool (get_briefing, find_stories, …) to read an article without leaving the conversation.

Input parameters:

- `id` (string, required): Article _id or slug

### `list_categories` (~16 tokens)

List all news categories with article counts.

### `list_sources` (~33 tokens)

List active news sources. Optionally filter by country code.

Input parameters:

- `country` (string): Filter by country code (optional)

### `get_stats` (~21 tokens)

Platform statistics: total articles, active sources, and today's output.

### `get_my_feed` (~52 tokens)

Personalised news feed based on the authenticated user's article likes and saves. Requires Authorization: Bearer <WorkOS access token>.

Input parameters:

- `limit` (number): Max articles, 1–20 (default 12)

### `get_trending_analytics` (~87 tokens)

Open analytics: trending topics, categories, keywords, and sources for any location or period. Part of Mukoko's open data policy.

Input parameters:

- `limit` (number): Max results per section, 1–20 (default 10)
- `location` (string): Country code, region, or city (optional)
- `period` (string): Time window (default: today)

### `detect_surge` (~89 tokens)

Detect sudden spikes in news coverage — compares last 24h against 7-day baseline. Surfaces unusual increases like crime up 5× in Bulawayo or a football surge in Ghana.

Input parameters:

- `limit` (number): Max surges to return, 1–20 (default 10)
- `location` (string): Country, region, or city (optional — omit for continent-wide)

### `get_content_analytics` (~56 tokens)

Open data breakdown of news coverage by category, country, and keyword for a given period.

Input parameters:

- `location` (string): Country, region, or city (optional)
- `period` (string): Time window (default: week)

### `trigger_enrichment` (~175 tokens)

Manually run the AI enrichment agent over existing articles (classification, keywords, entities, quality scoring). RESTRICTED to platform-team accounts — requires a WorkOS bearer token issued inside the platform-team org. By default enriches the most recent un-enriched articles; pass article_ids to target specific ones, or reset_attempts to re-run articles that previously hit the failure cap.

Input parameters:

- `article_ids` (array): Specific article IDs to (re)enrich (optional). Capped at 50.
- `limit` (number): How many un-enriched articles to enqueue, 1–50 (default 25). Ignored when article_ids is given.
- `reset_attempts` (boolean): Re-enrich even articles that already hit the failure cap (default false). Use sparingly — it re-bills AI.

### `drain_enrichment_backlog` (~96 tokens)

Drain the ENTIRE un-enriched article backlog, not just one batch. RESTRICTED to platform-team accounts (WorkOS bearer issued inside the platform-team org). Fire-and-forget: asks the pipeline worker to enrich un-enriched articles in batches (oldest first) until the backlog is clear, running independently of the automatic 10-minute sweep. Returns immediately; use trigger_enrichment for a single targeted batch instead.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nyuchi-mukoko-news/news#diagnostics

## Score history

- 2026-08-03: 59
- 2026-08-02: 58
- 2026-08-01: 58
- 2026-07-31: 57
- 2026-07-30: 59
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://news.mukoko.dev/mcp
- Repository: https://github.com/nyuchi/mukoko-news
- Website: https://news.mukoko.com/
- Changelog RSS feed: https://verifymcp.io/servers/nyuchi-mukoko-news/news/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/nyuchi-mukoko-news/news/changelog.json
- HTML version of this page: https://verifymcp.io/servers/nyuchi-mukoko-news/news