FaultDebug
Related Servers
Alternatives to FaultDebug
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients and agents to drive SpectraProbe's static analysis engine over stdio, exposing twelve tools for probing targets, inspecting metadata, strings, dependencies, symbols, imports, resources and JavaScript, searching evidence, creating reports, listing providers and checking analysis status.2MIT- FlicenseNot gradedqualityCmaintenanceEnables querying enterprise records and retention policies from any MCP client over stdio, with read-only tools for searching records, fetching retention verdicts, identifying archival candidates, summarizing departments, forecasting retentions, and viewing audit history.-
- AlicenseNot gradedqualityAmaintenanceEnables evidence-first binary and firmware analysis through MCP, exposing tools to initialize projects, analyze artifacts, query structured claims, export results, and run evaluations.Apache 2.0
- AlicenseAqualityBmaintenanceProvides read-only MCP tools to inspect imported history sources, list sessions, search literal text, and read paginated event history from a local SQLite index.42MIT
- AlicenseNot gradedqualityAmaintenanceExposes three read-only tools that list local Agent and MCP runtime candidates, inspect running processes, and check a live runtime against an approved artifact expectation. Returns explicit verdicts such as matched, stale, leaked, conflict, unknown, or not running without exposing argv, environment values, or file contents.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides read-only MCP tools to list archived snapshots, retrieve methodology and proof bundles, and verify supplied evidence bundles.MIT
TDQS
Scored across 24 tools
Many tools share overlapping read-only reporting purposes (e.g., get_incident_report, get_session_manifest, get_incident_slice, get_evidence_summary) and eight tools lack descriptions entirely, making it hard to distinguish trace-related tools like get_thread_trace, get_rpc_trace, get_timeline, and get_call_relations. Boundaries are unclear for a significant portion of the set.
All tool names use snake_case with a consistent verb_noun structure (get_, list_, check_, open_, collect_, discover_, query_, resolve_). No mixing of conventions or casing styles.
With 24 tools, the set is on the heavy side for a fault-debugging server, and several tools appear to overlap in function, suggesting opportunities for consolidation. Still, the domain is complex enough that many capabilities are plausibly needed.
The surface covers sessions, incidents, traces, artifacts, source citations, and provenance, and includes tools for opening/collecting faults, which suggests broad lifecycle coverage. Some write/update/delete operations may be missing, but the read-focused debugging scope appears mostly complete.