hermes agent mcp
Hermes Agent MCP readiness checker
Validate whether a Hermes Agent workspace is ready to expose MCP servers safely.
What this workflow solves
MCP failures usually hide in missing packages, tool visibility gaps, unsafe environment leakage, or server definitions that work in one surface but disappear in another.
How the check works
Paste the MCP server entry or tool catalog.
Check install state, transport type, secrets handling, and workspace visibility.
Export a receipt for the team member who owns the final launch.
Common risks to catch early
- Tools visible in CLI but not in Desktop or TUI
- Optional catalog installs not pinned before bootstrap
- Credentials passed into subprocess environments
- No test evidence before the gateway starts accepting work
Sample readiness receipt
Status: Needs fixes before production users depend on this route.
Evidence: Workspace notes mention the target surface, but do not yet prove callback host, tool visibility, secret handling, and operator handoff.
Recommended next action: Run the console, save the result, and unlock the complete Team report when the setup is ready for review.