Home / MCP registry index / io.github.srotzin/hive-mcp-morph
Hive Morph
io.github.srotzin/hive-mcp-morph in the official MCP registry.
Endpoint https://hive-mcp-morph.onrender.com/mcp. Source: github.com/srotzin/hive-mcp-morph.
The registry describes it as: HiveMorph polymorphic identity and capability tokens for autonomous agents
We read its 14 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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 every week.
Tools it advertises
morph_audit_recent morph_get_identity morph_list_supermodels morph_get_supermodel morph_carousel morph_brood_pending_approvals morph_brood_conversion morph_brood_all morph_brood_conversion_leaderboard morph_brood_for_supermodel morph_spawn_monitor_scan morph_money_flavor_probe morph_money_flavor_stats morph_auto_cull_scan
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-srotzin-hive-mcp-morph)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. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.