Infrabroker vs Terminal History Mcp

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
I
🖥️ Command Line
T
🖥️ Command Line
SummarySSH & Kubernetes access broker where the model never touches a credential: a separate signer mints per-operation ephemeral SSH certificates and bound ServiceAccount tokens, with a per-command allow/deny/approval firewall (POSIX-sh AST), dry-run, human-in-the-loop approvals, session recording and an Ed25519-chained audit log. Self-hosted Go binaries, GPLv3.Full-text search over your shell history (zsh / bash / fish) via SQLite FTS5. Local-only. 11-pattern secret redaction runs BEFORE insert. Captures cwd / exit code / duration via opt-in shell hook. Tools: searchhistory, recentindir, failedcommands, commandchains, reindex.
Quality signal25/100 (Emerging)23/100 (Emerging)
Install pathnpx · lownpx · low
Engagement 2 0 0 1 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView InfrabrokerView Terminal History Mcp
More alternatives to InfrabrokerMore alternatives to Terminal History McpCommand Line categoryCanonical compare URL

Other servers like Infrabroker