{"id":"templetwo-temple-bridge","name":"temple-bridge","af_score":50.2,"security_score":47.2,"reliability_score":32.5,"what_it_does":"Temple Bridge is a local MCP (Model Context Protocol) server that exposes tool-based access (8 tools, 3 resources) for an LLM-based workflow. It appears designed to connect an \"Action Layer\" repository (back-to-the-basics) with a \"Governance/Memory\" repository (threshold-protocols), using middleware to maintain state across MCP tool calls and a human-in-the-loop approval gate for command execution.","best_when":"You want a local, MCP-compatible agent that can perform controlled repository operations with an explicit human approval step before executing commands.","avoid_when":"You need a standardized, externally hosted API with strong auth, documented rate limits, or you cannot reliably enforce/monitor local sandboxing and approval behavior.","last_evaluated":"2026-03-30T15:40:07.827072+00:00","has_mcp":true,"has_api":false,"auth_methods":["Human-in-the-loop approval in LM Studio for command execution (described as 'Threshold Witness')"],"has_free_tier":false,"known_gotchas":["Command execution is gated by interactive approval; agents running without a human present may stall.","Tool timeouts are described (default 60s; configurable), so long-running commands may fail without retries.","The server relies on correct local configuration paths (TEMPLE_BASICS_PATH / TEMPLE_THRESHOLD_PATH) and LM Studio MCP connectivity."],"error_quality":0.0}