Skip to main content
Glama
UnboundCompute

lachesis-mcp

Official
by UnboundCompute
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lachesis-mcp

  • Ghidra MCP Server

    bethington
    A
    license
    A
    quality
    A
    maintenance
    Model Context Protocol server for Ghidra reverse engineering. 179 tools for decompilation, symbol management, cross-references, and binary analysis.
    8
    3,965
    Apache 2.0

Related Servers

  • Lore MCP Server

    jafreck
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables LLM agents to query a codebase's structural knowledge (symbols, imports, call graphs, etc.) via MCP, reducing tokens and improving correctness compared to raw file access.
    35 npm
    7
    MIT

  • Girder

    dhishwasher
    F
    license
    Not graded
    quality
    A
    maintenance
    Enables AI coding agents to query a semantic code graph over MCP, retrieving exact function source, definitions, callers/callees, impact analysis, and minimal test selection instead of whole files.
    12
    -

  • pyghidra-mcp

    clearbluejar
    A
    license
    Not graded
    quality
    B
    maintenance
    Exposes Ghidra reverse engineering capabilities via MCP, enabling LLMs and agents to analyze binaries, decompile, search, and edit programs headlessly or with GUI integration.
    426
    Apache 2.0

  • ghidraMCP

    albertlab0
    A
    license
    Not graded
    quality
    D
    maintenance
    An Model Context Protocol server that enables LLMs to autonomously reverse engineer applications by exposing Ghidra's decompilation and analysis tools. It allows AI agents to list code structures, rename methods, and analyze binaries directly through MCP-compatible clients.
    Apache 2.0
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

B3.4/5.0

Scored across 50 tools

Disambiguation2/5

Although each description is detailed, the set contains multiple near-overlapping families: component_boundary/cross_boundary_paths, flow/flow_pass/flow_skeleton, candidates/leads/scan, and skeleton/explain. An agent selecting among 50 tools will frequently face unclear boundaries, especially between value-flow, taint, and lead-generation tools.

Naming Consistency3/5

Names are uniformly snake_case and readable, but the grammatical pattern is mixed: some are verb_noun (load_graph, read_body), many are plural nouns (callers, hubs, candidates, leads), and some are single verbs (scan, explain, enrich). This is a readable mixed convention rather than a consistent verb_noun system.

Tool Count2/5

Fifty tools is far beyond the 3-15 well-scoped range and even beyond the 16-25 heavy range. The breadth reflects a comprehensive analysis pipeline, but many tools are pass-specific variants that could be consolidated or exposed as parameters.

Completeness4/5

The domain surface is remarkably broad: graph loading/building, call and value-flow navigation, lifecycle/guard/taint analysis, tests/specs/history, and pass management are all covered. Minor gaps exist such as no explicit graph inventory/status tool or graph unload, but agents can work around them.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources