Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

HexWitness

by siaginwversion 1.0.1i★ 2iRuns on your computerRepository ↗
Registry nameio.github.siaginw/hexwitness

How to install

What it does

Durable, build-scoped reverse-engineering evidence memory and query tools for AI agents.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Search & AI memory

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6381 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6051 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2361 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity6/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score18/100

Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install HexWitness. Follow https://mcp.popnx.com/i/siaginw-hexwitness.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server HexWitness for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "hexwitness": { "command": "npx", "args": [ "-y", "hexwitness", "agent" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the HexWitness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "hexwitness": {
          "command": "npx",
          "args": [
            "-y",
            "hexwitness",
            "agent"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use HexWitness and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using HexWitness or shows a HexWitness tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect HexWitness yet

HexWitness runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect HexWitness

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Search & AI memory that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server HexWitness for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user hexwitness -- npx -y hexwitness agent 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the HexWitness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user hexwitness -- npx -y hexwitness agent
  4. Type /mcp in Claude Code

    You should see HexWitness listed as connected

  5. Try it

    Use HexWitness and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using HexWitness or shows a HexWitness tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server HexWitness for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "hexwitness": { "command": "npx", "args": [ "-y", "hexwitness", "agent" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the HexWitness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use HexWitness and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using HexWitness or shows a HexWitness tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server HexWitness for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "hexwitness": { "type": "stdio", "command": "npx", "args": [ "-y", "hexwitness", "agent" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the HexWitness tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use HexWitness and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using HexWitness or shows a HexWitness tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use HexWitness💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user hexwitness -- npx -y hexwitness agent

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "hexwitness": {
      "command": "npx",
      "args": [
        "-y",
        "hexwitness",
        "agent"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "hexwitness": {
      "command": "npx",
      "args": [
        "-y",
        "hexwitness",
        "agent"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "hexwitness": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "hexwitness",
        "agent"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
53/wk
Licencei
No licence stated
Connection
Runs on your computer
Latest versioni
1.0.1
Published to registryi
Aug 12, 2026
Code last changedi
Nov 2, 2026
Maker
siaginw
Packages
npm: hexwitness
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account siaginw, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 18 days ago

  • ! Caution

    Has a licence

    GitHub could not identify the licence type; open the file to check

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for hexwitness@1.0.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/siaginw-hexwitness.svg)](https://mcp.popnx.com/en/servers/siaginw-hexwitness)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Search & AI memoryi

  • More stars than 83% of the other 6447 servers in this category
  • Published to the registry more recently than 25% of the other 6447 servers in this category
  • Basic checks equal to or better than 50% of the other 6447 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is HexWitness safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 18 days ago, and the latest version (1.0.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

by every-appWidely used★ 28.3KUpdated 6 days ago

Runs in the cloud✓ everyapp.com

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsWidely used★ 5.2KUpdated today

Runs in the cloud✓ service owner · exa.aiTried by the PopNx team

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

by MicrosoftDocsWidely used★ 2KUpdated 12 months ago

Runs in the cloud✓ service owner · microsoft.comTried by the PopNx team

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

by proxysoulGrowing★ 1.6KUpdated 2 months ago

Runs in the cloud✓ empryo.com
Compared with similar ones
This one
HexWitness
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesYesYesNoNo
Basic checks2/35/52/44/44/44/4
LicenseNOASSERTIONMITMITCC-BY-4.0NOASSERTIONApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Give your reverse-engineering agent a memory, a map, and receipts.

HexWitness turns static analysis, runtime captures, and human conclusions into one durable evidence graph.

Quick start · Why it matters · Examples · Docs · How it compares


Yesterday, your agent found the parser, mapped its callers, and proved which runtime event reached it. Today, a new chat opens and asks the live disassembler to discover everything again.

HexWitness stops that loop.

flowchart LR

V["Binary Ninja · IDA · Ghidra"] --> X["Reviewed evidence"] R["Frida · debugger · wire observer"] --> C["Sealed capture"] C --> X X --> E[("HexWitness memory")] E --> A["Your AI agent"] A --> Q["Answer with proof"] A -.->|one named gap| V

The live viewer remains the agent's eyes. HexWitness becomes its case file: tied to an exact build, searchable across tools, honest about conflicts, and ready for the next agent.

See it work in 60 seconds

Requirements: Git and Node.js 22.13 or newer.

npm install --global hexwitness

hexwitness setup hexwitness demo

The setup wizard connects HexWitness to Codex, Claude Code, Cursor, VS Code/Copilot, Claude Desktop, or generic MCP clients. It also installs guidance written for that agent. The MCP entry starts the local read-only daemon when needed, so there is no service choreography.

Now ask:

Use HexWitness to explain 0x401120 in build toy-v1.

Show proof, contradictions, and missing evidence separately.

The demo uses synthetic, redistributable evidence. No third-party binary data ships with HexWitness.

Prefer a checkout?

git clone https://github.com/siaginw/HexWitness.git

cd HexWitness npm install npm run demo npm run setup -- --client codex --viewer none --yes npm run doctor

Replace codex with claude-code, cursor, copilot, or generic as needed. The setup command resolves the checkout's absolute local runtime path, installs guidance tailored to the selected agent, and writes the MCP connection without requiring a global install. Restart the selected AI client after setup, then ask it to call hexwitness_health and hexwitness_contract. Both must succeed before using private evidence.

[!IMPORTANT]

The checked-in .mcp.json.example assumes npm install --global hexwitness. From a source checkout, run npm run setup instead of copying that example; setup records the correct local Node.js and bundled-runtime paths.

HexWitness installs as one command. The service, MCP transport, installer, capture pipeline, and adapter catalog live behind that command:

hexwitness agent                 # daemon autostart + MCP for AI clients

hexwitness serve # REST daemon only hexwitness adapters # list every included viewer/runtime adapter hexwitness adapters binary-ninja # print one adapter's exact path and capabilities hexwitness contract # inspect the stable 1.x public contract hexwitness backup ./evidence.db # create and verify a consistent snapshot

Official MCP Registry identity: io.github.siaginw/hexwitness. Registry-aware clients discover the same local stdio server published through npm; its declared launch contract is hexwitness agent.

The npm package ships one bundled runtime instead of exposing its internal module tree. Python remains only in the thin Binary Ninja, IDA, and Ghidra exporters because those products expose their supported automation APIs through Python. Large JSONL exports and long captures are streamed through atomic ingest and disk-backed normalization instead of being loaded wholesale into memory.

Why HexWitness feels different

Most RE integrations solve access: let an agent read a decompiler, debugger, or trace. HexWitness solves continuity: keep the useful result after that tool, build, or chat is gone.

ApproachExcellent forThe gap HexWitness fills
Viewer MCPLive decompilation, xrefs, renames, analysis controlFindings are session-scoped unless promoted
Notes and reportsHuman narrativeHard to query, compare, or trace back to exact evidence
General agent memoryPreferences and broad project contextNo dedicated build, address, call-graph, capture, or provenance contract
HexWitnessDurable RE evidence and runtime reconstructionPairs with viewers instead of replacing them

That makes HexWitness especially useful when:

  • the binary changes and addresses move;
  • several agents or analysts share work;
  • static code must line up with runtime behavior;
  • a conclusion needs a reproducible chain of evidence;
  • a failed capture must be compared with a working one;
  • “we think” needs to become “we proved.”

Read the honest category comparison in Why HexWitness.

Ask real questions

Users ask about the target. The agent chooses the tools.

Which function validates frame length before dispatch?

Reuse retained evidence first. Inspect a live viewer only if one exact edge is missing.

Compare the working and failing login captures.

Find the first meaningful divergence, then resolve its static consumer.

Where is this UUID used, which class owns it, and did its field offset change

between builds?

HexWitness gives agents first-class queries for builds, functions, classes, UUIDs, types, fields, vtables, calls, xrefs, paths, dataflow, captures, contradictions, coverage, evidence gaps, durable investigations, failed attempts, challenges, and discovery-only retrieval. Four MCP prompts package investigation, runtime comparison, live-finding promotion, and adversarial evidence-review workflows.

One investigation loop

  1. Remember. Query retained evidence before touching a live tool.
  2. Pin. Select the exact artifact build; never carry an address across builds by habit.
  3. Resolve. Search the subject, then read its full evidence dossier.
  4. Narrow. Traverse only the calls, fields, slices, or capture window needed.
  5. Challenge. Surface provenance, confidence, and contradictory claims.
  6. Escalate. If proof ends, name the smallest missing live observation.
  7. Promote. Export that bounded result so the next investigation starts smarter.

For longer work, deterministic playbooks seed persistent checklists and operation budgets. Failed methods stay searchable. An evidence challenge surfaces opposition, unsupported claims, and open gaps without allowing agent consensus to inflate confidence.

Agents can also run allowlisted local RE utilities through one explicit MCP tool: argv-only, cwd-rooted, timed, output-capped, and receipt-producing. It is not an OS sandbox. Tool output remains an observation until promoted through the evidence model. No environment enable switch or separate model-provider key is required. See Investigation workbench.

The database remembers evidence. A separate privacy-safe activity store remembers operation hashes, timing, status, and counts—never prompts, arguments, or returned evidence.

Runtime capture without command soup

Collectors place conventional files and a small manifest in one private folder:

roundtrip/

├── capture.json ├── wire.jsonl ├── hooks.jsonl ├── screen.mp4 └── context.json

Then:

hexwitness capture ./private/roundtrip

HexWitness checks the required roles and action markers, copies artifacts into an isolated private pack, normalizes a safe timeline by removing secret fields and replacing payloads with length plus SHA-256, seals checksums, verifies integrity, and imports the evidence. Missing or empty baseline artifacts fail closed. A failed normalization leaves the source pack recoverable.

See Capture packs for collector and scenario contracts.

Works with your stack

ToolDurable bridge
Binary NinjaDeep JSONL exporter plus optional official Binary Ninja MCP live viewer
IDA / IDAPythonFunctions, strings, imports, references, blocks, and optional Hex-Rays pseudocode plus live MCP
GhidraFunctions, strings, imports, references, blocks, types, fields, and enum exporter
Frida 17Narrow semantic-event observer and fail-closed JSONL normalizer
Other toolsVersioned adapter manifest and vendor-neutral JSONL schema

HexWitness does not ship a weaker disassembler inside the project. Viewer MCPs provide live eyes. Exporters turn reviewed findings into portable memory. Read Viewer MCP bridges and the Adapter SDK.

One truth, three interfaces

InterfaceBest use
MCPAgent-led investigations, read-only evidence tools, and one explicitly open-world local-tool runner
CLIImport, capture lifecycle, automation, recovery, and direct queries
RESTLocal read-only integration with a published route manifest

All three read the same SQLite evidence graph. Imports are transactional and idempotent. Addresses remain canonical hexadecimal strings, including unsigned 64-bit values.

Evidence, not vibes

  • Build — exact artifact identity and analysis provenance.
  • Entity — function, type, class, field, vtable, runtime object, or project-defined object.
  • Edge — call, reference, ownership, inheritance, dataflow, or runtime relationship.
  • Evidence — an observation with source, time, classification, and confidence.
  • Claim — an interpretation linked to supporting or opposing evidence.
  • Capture — a sealed scenario with artifacts, markers, events, and checksums.
  • Gap — the next missing fact needed to prove a behavior.

Conflicting claims remain visible. Unknown behavior becomes a worklist, not a fabricated answer.

Private by default

raw private material  →  normalized project evidence  →  synthetic public fixtures
  • Daemon binds to localhost and serves GET-only queries, including a loopback-only dashboard.
  • Non-local binding requires an API token and still needs trusted TLS transport.
  • Executable bytes and decompiler text are not exported by default.
  • Capture normalization recursively removes common secret and payload fields.
  • Public-release audit blocks credentials, captures, dumps, proprietary binary formats, large embedded payloads, and personal paths.

Read Privacy and Security before importing sensitive work.

Documentation

Start hereWhat it answers
Getting startedCan I prove the full local loop?
Why HexWitnessWhy not just use notes, a viewer MCP, or generic memory?
AI setup wizardWhat gets installed for each agent?

| [AI-first workflows](docs/AI-FIRST-WORKFLO

Only the beginning is shown; read the rest in the repo