aegis-re
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aegis_inspect_binaryB | Inspects binary format, architecture, bitness, mitigations (NX, PIE, Canary), entropy, and high-risk API imports. |
| aegis_triage_vulnerabilitiesB | Scans decompiled C/C++ or source code for CWE security flaws (buffer overflow, command injection, format strings, weak RNG, hardcoded keys). |
| aegis_calculate_entropyA | Calculates Shannon entropy (0.0 to 8.0) of a binary or byte payload to detect packing, obfuscation, or encryption. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
aegis_inspect_binary already reports entropy, while aegis_calculate_entropy is a dedicated entropy calculator, creating clear overlap. aegis_triage_vulnerabilities is distinct, and descriptions help clarify the broad-profile versus focused-entropy distinction, but the boundary is still blurry.
All three tools use the same aegis_ prefix and follow a consistent verb_noun pattern: inspect_binary, triage_vulnerabilities, calculate_entropy. Naming is highly predictable and readable.
Three tools is a lean but reasonable scope for a focused binary triage server, with no excessive surface. However, aegis_calculate_entropy is partially redundant with aegis_inspect_binary, so not every tool fully earns its place.
The set covers binary metadata/mitigations, vulnerability pattern scanning, and entropy/packing detection, which supports core triage workflows. But for a reverse-engineering server, it lacks obvious operations such as disassembly, string extraction, symbol/function listing, and report export.