# Mamiriro (MEGMIS) (remote · megmis-api.onrender.com)

PROTOTYPE: Zimbabwe weather, geo, safe routing & journey risk via REST+MCP (stdio/HTTP).

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `megmis-api.onrender.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis-api.md), [page](https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis-api)
- pypi · `megmis`: 49/100, [markdown](https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis.md), [page](https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis)

## Channel facts

- Endpoint: `https://megmis-api.onrender.com/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 31/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 1038 tokens (~43/item across 24 items; 24 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Mamiriro (MEGMIS) MCP server?

Mamiriro (MEGMIS) is a hosted endpoint at https://megmis-api.onrender.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http walter-kudzai-kamanga-megmis 'https://megmis-api.onrender.com/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "walter-kudzai-kamanga-megmis": {
      "url": "https://megmis-api.onrender.com/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "walter-kudzai-kamanga-megmis": {
      "type": "http",
      "url": "https://megmis-api.onrender.com/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.walter-kudzai-kamanga-megmis]
url = "https://megmis-api.onrender.com/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "walter-kudzai-kamanga-megmis": {
      "type": "remote",
      "url": "https://megmis-api.onrender.com/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add walter-kudzai-kamanga-megmis --url 'https://megmis-api.onrender.com/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  walter-kudzai-kamanga-megmis:
    url: "https://megmis-api.onrender.com/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "walter-kudzai-kamanga-megmis": {
      "Transport": "http",
      "Url": "https://megmis-api.onrender.com/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add walter-kudzai-kamanga-megmis -t streamable-http -u 'https://megmis-api.onrender.com/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "walter-kudzai-kamanga-megmis": {
      "type": "http",
      "url": "https://megmis-api.onrender.com/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-11-20 (score 63, +1)

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

### 2026-11-18 (score 62, +1)

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

### 2026-11-17 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 61)

First indexed and scored.

## MCP tools (24)

### `get_current_weather` (~31 tokens)

Current weather for a location ({lat,lon} or {name}).

Input parameters:

- `location` (object, required)

### `get_forecast` (~31 tokens)

Daily forecast (1-14 days).

Input parameters:

- `days` (integer)
- `location` (object, required)

### `get_hourly_forecast` (~38 tokens)

Hourly forecast for a specific ISO date (YYYY-MM-DD).

Input parameters:

- `date` (string, required)
- `location` (object, required)

### `get_weather_alerts` (~29 tokens)

Active weather alerts; official warnings labelled separately from model-derived.

Input parameters:

- `location` (object, required)

### `compare_weather` (~22 tokens)

Compare current weather across multiple locations.

Input parameters:

- `locations` (array, required)

### `get_historical_weather` (~40 tokens)

Historical weather observations between ISO dates.

Input parameters:

- `end_date` (string, required)
- `location` (object, required)
- `start_date` (string, required)

### `get_air_quality` (~25 tokens)

Air quality index and pollutants for a location.

Input parameters:

- `location` (object, required)

### `get_agricultural_conditions` (~24 tokens)

Agricultural / growing-condition indicators.

Input parameters:

- `location` (object, required)

### `analyze_weather_risk` (~44 tokens)

Activity-based weather risk (e.g. outdoor_wedding) with recommendations.

Input parameters:

- `activity` (string, required)
- `date`
- `location` (object, required)

### `recommend_outdoor_activities` (~31 tokens)

Suitability scores for common outdoor activities.

Input parameters:

- `date`
- `location` (object, required)

### `geocode` (~25 tokens)

Geocode an address or place name to coordinates.

Input parameters:

- `address` (string, required)

### `reverse_geocode` (~31 tokens)

Reverse-geocode coordinates to an address.

Input parameters:

- `lat` (number, required)
- `lon` (number, required)

### `find_nearby_places` (~41 tokens)

Find nearby places by optional category within radius_m.

Input parameters:

- `category`
- `location` (object, required)
- `radius_m` (integer)

### `get_emergency_facilities` (~33 tokens)

Nearby emergency facilities (hospital, police, fire).

Input parameters:

- `location` (object, required)
- `type`

### `optimize_route` (~70 tokens)

Ranked routes with cost_breakdown and explanation (shortest is not always best).

Input parameters:

- `departure_time`
- `destination` (object, required)
- `origin` (object, required)
- `priorities`
- `profile` (string)
- `vehicle_class` (string)
- `waypoints`

### `create_journey` (~39 tokens)

Create an active journey from a route_id returned by optimize_route (requires auth).

Input parameters:

- `api_key`
- `route_id` (string, required)

### `reroute` (~48 tokens)

Recompute alternatives for an active journey (requires auth).

Input parameters:

- `api_key`
- `current_position` (object, required)
- `journey_id` (string, required)
- `reason` (string)

### `get_route_conditions` (~33 tokens)

Weather, traffic and road-condition summary for a route or corridor.

Input parameters:

- `corridor`
- `route_id`

### `report_road_condition` (~58 tokens)

Submit a crowdsourced road-condition report (requires auth + road:write).

Input parameters:

- `api_key`
- `evidence_refs`
- `location` (object, required)
- `severity` (integer, required)
- `type` (string, required)

### `get_road_incidents` (~30 tokens)

List road incidents for an area or corridor.

Input parameters:

- `area`
- `corridor`

### `assess_journey_risk` (~95 tokens)

Composite journey risk from weather + routing + road; persists when tenant is known.

    Tenant resolution order: explicit api_key arg → request ContextVar (X-API-Key on /mcp)
    → default demo tenant when persistence is on.

Input parameters:

- `activity` (string)
- `api_key`
- `destination` (object, required)
- `origin` (object, required)
- `profile` (string)

### `get_traffic_congestion` (~27 tokens)

Traffic sub-module congestion estimate for a corridor.

Input parameters:

- `corridor` (string, required)

### `list_service_packs` (~23 tokens)

List Insurance / GovTech commercial service packs (Gen 4).

### `run_service_pack` (~65 tokens)

Run a commercial pack: insurance.corridor | govtech.emergency | govtech.mobility.

Input parameters:

- `api_key`
- `destination`
- `location`
- `origin`
- `pack_id` (string, required)
- `profile` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis-api#diagnostics

## Score history

- 2026-11-21: 63
- 2026-11-20: 63
- 2026-11-19: 62
- 2026-11-18: 62
- 2026-11-17: 61
- 2026-11-16: 61

## Common questions

### What is the Mamiriro (MEGMIS) MCP server?

Mamiriro (MEGMIS) is an MCP server listed in the public MCP registry as io.github.walter-kudzai-kamanga/megmis. PROTOTYPE: Zimbabwe weather, geo, safe routing & journey risk via REST+MCP (stdio/HTTP). This page covers its hosted endpoint (https://megmis-api.onrender.com/mcp/).

### Is the Mamiriro (MEGMIS) MCP server safe to use?

Mamiriro (MEGMIS) scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Mamiriro (MEGMIS) MCP server expose?

Mamiriro (MEGMIS) exposes 24 tools: get_current_weather, get_forecast, get_hourly_forecast, get_weather_alerts, compare_weather, and 19 more. Their descriptions and schemas cost roughly 933 tokens of context every time the server is loaded.

### Does the Mamiriro (MEGMIS) MCP server require authentication?

No. We connected to Mamiriro (MEGMIS) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Mamiriro (MEGMIS) MCP server still maintained?

Mamiriro (MEGMIS) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Mamiriro (MEGMIS) MCP server?

VerifyMCP ran 13 checks on Mamiriro (MEGMIS), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://megmis-api.onrender.com/mcp/
- Repository: https://github.com/walter-kudzai-kamanga/megmis
- Changelog RSS feed: https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis-api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis-api.json
- HTML version of this page: https://verifymcp.io/servers/walter-kudzai-kamanga-megmis/megmis-api
