Skip to main content
Glama
jnjaeschke

pernosco-mcp

by jnjaeschke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pernosco-mcp

No user-submitted related servers found.

    Related Servers

    • gdb_mcp

      airfloats
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to control GDB debugging sessions, including breakpoint management, thread analysis, and variable inspection, using the GDB/MI protocol.
      22
      1
      MIT

    • gdb and rr Debugging

      schuay
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes GDB debugging as tools. An AI assistant can set breakpoints, run programs, step through code, inspect variables and memory, and examine registers — all via structured tool calls. Reverse debugging with rr is also supported.
      34
      3
      MIT

    • GDB-MCP

      hnmr293
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides programmatic access to the GNU Debugger (GDB), enabling AI models to interact with GDB through natural language for debugging tasks.
      9
      Apache 2.0

    • elim-mcp

      DevAsadYasin
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives coding agents a persistent, chained memory of debugging investigations, tracking what's been tried, ruled out, and solved across sessions and scopes.
      13 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, covering navigation, state querying, session management, and annotations. Overlaps are minimal (e.g., watchpoint_history vs. watch_variable are differentiated by input type), and descriptions clearly delineate boundaries.

    Naming Consistency5/5

    All tool names use snake_case and follow a consistent verb_noun or noun pattern (e.g., find_breakpoint_hits, session_status, source_read). There is no mixing of conventions, making the naming predictable and easy to reason about.

    Tool Count4/5

    With 20 tools, the count is slightly above the typical well-scoped range (3-15), but each tool addresses a specific debugging need in a complex domain. The surface is neither bloated nor insufficient, earning a 4.

    Completeness4/5

    The tool set covers the core reverse debugging workflow: session management, navigation, source inspection, stack traces, variable/watchpoint history, expression evaluation, and process/thread hierarchy. Minor gaps (e.g., no explicit register inspection) exist, but the overall coverage is strong.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources