Skip to main content
Glama
Faceless0x7

AdaptixC2 MCP Server

by Faceless0x7
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

bof_creds

Extract Windows credentials including SAM hashes, LSA secrets, cached domain credentials, and browser cookies using various BOF techniques.

Instructions

Creds-BOF: Windows credential extraction.

askcreds [-p prompt] [-n note] [-t wait_time_secs] [--async] Prompt user for credentials via fake dialog. Example: askcreds -p "Windows Update"

get-netntlm [--no-ess] Retrieve NetNTLM hash (Internal Monologue). Example: get-netntlm --no-ess

hashdump Dump SAM hashes (requires admin). Auto-saves to credentials tab.

lsadump_secrets Dump LSA secrets from SECURITY hive (requires SYSTEM). Auto-saves service credentials.

lsadump_sam Dump SAM hashes via lsadump::sam (requires admin).

lsadump_cache Dump cached domain credentials DCC2/MSCacheV2 (requires SYSTEM).

nanodump [--write path] [--valid] [--ppl-dump] [--kdump] ... Dump LSASS via syscalls. Example: nanodump --write C:\Windows\Temp\lsass.dmp

nanodump_ppl_dump Bypass PPL and dump LSASS (PPL-dump variant).

nanodump_ppl_medic Bypass PPL and dump LSASS (PPL-medic variant).

nanodump_ssp Load a Security Support Provider (SSP) into LSASS.

cookie-monster [--edge] [--chrome] [--firefox] [-t target_user] Locate and copy browser cookie files.

underlaycopy <MFT|Metadata> [-w destination] [--download] Copy file using low-level NTFS (MFT/Metadata mode). Example: underlaycopy MFT C:\Windows\System32\notepad.exe -w C:\temp\copy.exe

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
commandYes
argsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses some requirements (e.g., admin/SYSTEM privileges) and side effects (auto-saves to credentials tab). However, with no annotations, it could be more thorough about safety, data persistence, and error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy and dense with multiple subcommand details. It lacks a concise front-loaded summary, and the structure, while organized, could be more streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers subcommands and their arguments well, but it omits details about the output schema (though not required) and the 'agent_id' parameter. It is complete enough for the tool's complexity but has gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema coverage is 0%, the description effectively explains the 'command' and 'args' parameters through examples and usage strings. It adds meaning beyond the schema, though a direct mapping to parameters would be clearer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool is for Windows credential extraction and lists specific subcommands. However, it does not differentiate from sibling tools like bof_kerbeus or bof_lateral, which may also deal with credentials.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description only lists subcommands without explaining the appropriate context for each or when to choose this tool over others.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Faceless0x7/AdaptixC2-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server