Home / MCP registry index / io.github.walter-kudzai-kamanga/megmis
Mamiriro (MEGMIS)
io.github.walter-kudzai-kamanga/megmis in the official MCP registry.
Endpoint https://megmis-api.onrender.com/mcp/. Source: github.com/walter-kudzai-kamanga/megmis.
The registry describes it as: PROTOTYPE: Zimbabwe weather, geo, safe routing & journey risk via REST+MCP (stdio/HTTP).
We read its 24 tools on 2026-11-16. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http megmis https://megmis-api.onrender.com/mcp/{
"mcpServers": {
"megmis": {
"url": "https://megmis-api.onrender.com/mcp/"
}
}
}code --add-mcp '{"name":"megmis","type":"http","url":"https://megmis-api.onrender.com/mcp/"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
get_current_weather get_forecast get_hourly_forecast get_weather_alerts compare_weather get_historical_weather get_air_quality get_agricultural_conditions analyze_weather_risk recommend_outdoor_activities geocode reverse_geocode find_nearby_places get_emergency_facilities optimize_route create_journey reroute get_route_conditions report_road_condition get_road_incidents assess_journey_risk get_traffic_congestion list_service_packs run_service_pack
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-16):
ed2e7fe9ecf6315a. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/io-github-walter-kudzai-kamanga-megmis)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| Mu mu.micro/mu | 173 tools, nothing matched 2026-11-11 |
| Gillby io.github.OneWave-AI/gillby | 120 tools, nothing matched 2026-11-14 |
| Portugal (public data) io.github.ThiagoJacobLannes/portugal-mcp | 56 tools, nothing matched 2026-11-11 |
| profullstack-mcp com.profullstack/profullstack-mcp | 53 tools, nothing matched 2026-11-11 |
| Aviation Weather io.github.pipeworx-io/aviation-weather | 52 tools, nothing matched 2026-11-18 |
| Noaa Swpc io.github.pipeworx-io/noaa-swpc | 51 tools, nothing matched 2026-11-11 |