How do I install Fathom?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Fathom need an API key?

No required environment variable is listed on this record.

What transport does Fathom use?

Fathom runs locally over stdio.

When was Fathom last checked?

Last checked 2026-11-07. Reverse-engineering tools for agents over MCP/A2A, with evidence-carrying findings.

Fathom MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

mcpb https://github.com/qompassai/fathom/releases/download/v1.0.0/fathom-mcp-1.0.0-linux-x64.mcpb

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add ai.qompass-fathom -- mcpb https://github.com/qompassai/fathom/releases/download/v1.0.0/fathom-mcp-1.0.0-linux-x64.mcpb

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "ai.qompass-fathom": {4      "command": "mcpb",5      "args": [6        "https://github.com/qompassai/fathom/releases/download/v1.0.0/fathom-mcp-1.0.0-linux-x64.mcpb"7      ]8    }9  }10}

claude_desktop_config.json

Local · mcpbPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.0.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

fathom

Rust port of REA (Reverse Engineer Anything): one provider-neutral MCP server for reverse engineering — native binaries, JavaScript/Electron applications, .NET assemblies, web captures, EVM bytecode, and process behavior — where every result is an evidence envelope that states what was observed, what was derived, what was not examined, and what the provider cannot establish.

The design is specified in SPEC.md: capability inventory mapped from upstream's public contracts, per-capability Rust strategy, evidence and error models, a deterministic fail-closed policy engine, and the staging plan. Design source: morluto/rea (MIT), credited in NOTICE; no upstream code is used.

Why a Rust port

Upstream REA is TypeScript/Node distributed through npm. This port exists to keep the capability on a Rust-first, pinned, auditable supply chain — the estate's standing direction (SPEC §1).

Shape

fathom-core — config, error contracts, evidence model, policy, tool registry, confinement, bounded processes.
fathom-mcp — MCP stdio + streamable HTTP transports.
fathom-a2a — signed A2A agent card (JCS + Ed25519).
fathom-native — Ghidra headless provider + binary layout (goblin).
fathom-js — JavaScript/Electron static analysis (oxc) + ASAR.
fathom-managed — .NET PE/CLI metadata (manual ECMA-335).
fathom-observe — process capture, HAR reading, EVM selectors.
fathom-cli — the fathom binary (serve, card, doctor, one-shot analysis).

Build

nix build          # or: nix develop, then cargo build --workspace
cargo test --workspace

License

This project is licensed under the Apache License, Version 2.0.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Fathom?

Does Fathom need an API key?

What transport does Fathom use?

When was Fathom last checked?

Documentation

fathom

Why a Rust port

Shape

Build

License