Headron Mind: hosted verification planning and proof for AI coding agents, over MCP and API.
Scored across 2 tools
The two tools have clearly distinct purposes: one plans gates from change metadata, while the other reads documentation. There is no realistic risk of selecting one when the other is intended.
Both names follow the same predictable verb_noun pattern: plan_change and read_document. The convention is consistent and readable.
Two tools is quite thin for a server that appears to support a planning/gating workflow. It may be intentionally minimal, but the surface feels borderline under-scoped.
The server exposes only a single planning action plus documentation retrieval. There is no way to discover change classes, risk modifiers, validate a plan, retrieve previous plans, or otherwise complete a gating lifecycle, leaving significant gaps.
Plan gates from a declared change class and risk modifiers. Requires a paid Mind API key in the Authorization header or api_key parameter; does not inspect a project or run gates.
Inputs: change_class (required), api_key, risk_modifiers.
Read public Headron documentation or its agent guide. This cannot inspect a local project.
Inputs: document (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.