Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Mamiriro (MEGMIS)

REMOTE · MEGMIS-API.ONRENDER.COM · 2 COMPONENTS

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

63 Trust /100

Last scanned (22 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability31
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 1038 tokens (~43/item across 24 items; 24 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://megmis-api.onrender.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 8d72a13c2c41648513b9d014eb5e0339
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of megmis-api.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
onrender.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://megmis-api.onrender.com/mcp/ Verified 200
http (plaintext) http://megmis-api.onrender.com/mcp/ HTTPS enforced 301 https://megmis-api.onrender.com/mcp/
MCP tools · 24 exposed · ~933 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_weather_risk ~44

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

NameTypeReqDescription
activitystringyes–
date–––
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

assess_journey_risk ~95

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.

NameTypeReqDescription
activitystring––
api_key–––
destinationobjectyes–
originobjectyes–
profilestring––

Structured output declared, but exposes no named fields.

No examples provided.

compare_weather ~22

Compare current weather across multiple locations.

NameTypeReqDescription
locationsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

create_journey ~39

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

NameTypeReqDescription
api_key–––
route_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_nearby_places ~41

Find nearby places by optional category within radius_m.

NameTypeReqDescription
category–––
locationobjectyes–
radius_minteger––

Structured output declared, but exposes no named fields.

No examples provided.

geocode ~25

Geocode an address or place name to coordinates.

NameTypeReqDescription
addressstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_agricultural_conditions ~24

Agricultural / growing-condition indicators.

NameTypeReqDescription
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_air_quality ~25

Air quality index and pollutants for a location.

NameTypeReqDescription
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_current_weather ~31

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

NameTypeReqDescription
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_emergency_facilities ~33

Nearby emergency facilities (hospital, police, fire).

NameTypeReqDescription
locationobjectyes–
type–––

Structured output declared, but exposes no named fields.

No examples provided.

get_forecast ~31

Daily forecast (1-14 days).

NameTypeReqDescription
daysinteger––
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_historical_weather ~40

Historical weather observations between ISO dates.

NameTypeReqDescription
end_datestringyes–
locationobjectyes–
start_datestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_hourly_forecast ~38

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

NameTypeReqDescription
datestringyes–
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_road_incidents ~30

List road incidents for an area or corridor.

NameTypeReqDescription
area–––
corridor–––

Structured output declared, but exposes no named fields.

No examples provided.

get_route_conditions ~33

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

NameTypeReqDescription
corridor–––
route_id–––

Structured output declared, but exposes no named fields.

No examples provided.

get_traffic_congestion ~27

Traffic sub-module congestion estimate for a corridor.

NameTypeReqDescription
corridorstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_weather_alerts ~29

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

NameTypeReqDescription
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_service_packs ~23

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

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

optimize_route ~70

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

NameTypeReqDescription
departure_time–––
destinationobjectyes–
originobjectyes–
priorities–––
profilestring––
vehicle_classstring––
waypoints–––

Structured output declared, but exposes no named fields.

No examples provided.

recommend_outdoor_activities ~31

Suitability scores for common outdoor activities.

NameTypeReqDescription
date–––
locationobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

report_road_condition ~58

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

NameTypeReqDescription
api_key–––
evidence_refs–––
locationobjectyes–
severityintegeryes–
typestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

reroute ~48

Recompute alternatives for an active journey (requires auth).

NameTypeReqDescription
api_key–––
current_positionobjectyes–
journey_idstringyes–
reasonstring––

Structured output declared, but exposes no named fields.

No examples provided.

reverse_geocode ~31

Reverse-geocode coordinates to an address.

NameTypeReqDescription
latnumberyes–
lonnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

run_service_pack ~65

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

NameTypeReqDescription
api_key–––
destination–––
location–––
origin–––
pack_idstringyes–
profilestring––

Structured output declared, but exposes no named fields.

No examples provided.

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.

remote · megmis-api.onrender.com

# add to Claude Code
claude mcp add --transport http walter-kudzai-kamanga-megmis 'https://megmis-api.onrender.com/mcp/'
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.