LLMxRay-MCP
Related Servers
Alternatives to LLMxRay-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides AI agents with real-time cognitive health monitoring, detecting context rot through token utilization, retrieval accuracy, and session fatigue analysis.49 npm13MIT
- AlicenseAqualityAmaintenanceRe-debugging Solved Failures? No Way. 500+ Evidence-graded fix lessons, One MCP Call-->https://misakanet.org112,199 npm861 PyPI553Apache 2.0
- AlicenseCqualityCmaintenanceProfessional local context management and system diagnostic tools for AI IDEs (Cursor, Trae, Antigravity, Windsurf).3684 npm1MIT
- AlicenseAqualityBmaintenanceShows what is consuming your agent context window before a session starts: always-loaded skill descriptions ranked by token cost, skills installed more than once under different names, CLAUDE.md/AGENTS.md sizes including what their @import lines pull in, and MCP servers configured across clients. Read-only: no child processes, no network.591 npmMIT
- AlicenseAqualityCmaintenanceEnables any AI, even a small local model, to work on real and large projects without getting lost, by compactly reporting project structure, exactly what is broken, whether a change truly passes verification, and which errors were already fixed before. It also remembers each project's past mistakes and groups errors by cause so the agent can follow a clear next step instead of looping.9BSD 3-Clause
- AlicenseNot gradedqualityDmaintenanceEnables LLM clients to inspect local dev environments—Docker container health, pnpm workspace integrity, and stuck process detection—without manual terminal copy-pasting.MIT
TDQS
Scored across 7 tools
Each of the four turn-reading tools is explicitly framed around one distinct question (verdict vs one turn full vs sequence vs before/after), and their descriptions cross-reference each other to steer selection. The prospective estimate_my_prompt is cleanly separated from the retrospective read_my_last_turn despite both touching prompt tokens. No tool pair genuinely overlaps.
A predictable verb_..._noun pattern holds throughout (estimate_, list_, diagnose_, read_, compare_). Minor deviations exist: some tools carry the 'my' owner marker while list_local_models omits it, and both read_ and list_ are used for read-like operations. Still readable and largely uniform.
Seven tools is well-scoped for a focused Ollama/LLMxRay observability server. Every tool maps to a distinct stage (pre-flight, inventory, per-turn, aggregate, server health) and none feels redundant.
The read-only observation domain is covered across pre-flight estimate, model inventory, single-turn detail, turn sequence, before/after comparison, and server status. Gaps are minor for a read-only surface (no way to change settings or inspect retained raw request text via MCP), though the description notes settings live on the Live page.