PerfLens MCP Server
Related Servers
Alternatives to PerfLens MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first CLI and MCP server for turning Xcode Instruments artifacts into bounded, agent-sized evidence, with support for analyses like Time Profiler, Allocations, Network, and more.2MIT
- AlicenseAqualityCmaintenanceA comprehensive Linux system performance profiler with MCP remote invocation support, featuring advanced process profiling and flame graph generation.102Apache 2.0
- FlicenseAqualityDmaintenanceEnables LLMs to analyze Linux perf data files using 26 perf analysis commands, including report, script, annotate, and more, through typed tool parameters.26-
- AlicenseBqualityBmaintenanceEnables any MCP client to plan and run verifiable analysis of engine hot-fire and bench test data through tools that open runs, segment phases, check sensor health, redlines, valve response and oscillations, compare simulations, verify every reported number against an evidence ledger, and write HTML reports. All findings stay traceable and reproducible from deterministic tool calls rather than raw samples.550 PyPIMIT
- FlicenseNot gradedqualityBmaintenanceEnables agents to autonomously diagnose Linux performance issues by exposing production-debugging primitives such as perf, strace, /proc, flamegraphs, and eBPF as safe, structured, budgeted tools.-
- FlicenseNot gradedqualityAmaintenanceEnables agents to gather bounded, reproducible runtime evidence by coordinating local profilers, benchmark tools, and trace processors against explicit artifacts or captured commands. It exposes typed analysis and capture operations over MCP that return provenance-tracked results inline, with optional durable preservation and replay of prior evidence.-
TDQS
Scored across 38 tools
Several tool families have dangerously similar names and overlapping purposes, especially the three authorize_docker_*_session tools, the three collect_docker_* tools, and the inspect_*_capability/capabilities tools. Though the descriptions are explicit and clarify boundaries, an agent would need to read long, nuanced descriptions carefully to avoid misselecting the wrong authorization or collection mode.
Tool names overwhelmingly follow a clear verb_noun snake_case pattern, and there is no mixing of camelCase or wildly different conventions. Minor inconsistencies exist in modifier placement (managed_docker vs docker_optimization) and singular/plural mismatches like capabilities vs capability, but the overall naming style is predictable.
38 tools is well above the 25+ threshold that indicates an overgrown surface. The workflows are complex, but the count is unwieldy and many tools are fine-grained variations of the same operation family, making the set feel heavier than its core purpose requires.
The tool set covers the apparent performance-analysis and Docker-optimization domain broadly: inspection, authorization, collection, analysis, verification, comparison, source resolution, diagnosis, and cleanup. Minor gaps like generic artifact deletion or session-status listing exist, but agents can work around them via read_artifact_page and the existing lifecycle tools.