Fathom
MCPB · LINUX-X64
Reverse-engineering tools for agents over MCP/A2A, with evidence-carrying findings.
Available components
Last scanned (7 hours ago)
Scores higher than 75% of MCPB servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1115 tokens (~44/item across 25 items; 25 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Oct 26 35
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Analysed mcpb/https://github.com/qompassai/fathom/releases/download/v0.1.1/fathom-mcp-0.1.1-linux-x64.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_art_style ~63
Measured style spec of an image or GIF: palette, grade statistics, shading model, animation timing grammar, sheet geometry
| Name | Type | Req | Description |
|---|---|---|---|
| palette_colors | integer | – | Palette clusters to extract (default 8) |
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
analyze_function ~36
Function dossier: listing, bounded decompile, callers, callees
| Name | Type | Req | Description |
|---|---|---|---|
| function | string | yes | – |
| target | string | yes | – |
No output schema declared.
No examples provided.
analyze_javascript_application ~39
Static analysis of a JS/Electron application: modules, graph, IPC boundaries
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
apply_style_via_lumen ~137
Grade an image with lumen's style engine (stdio MCP style_apply) and verify the output against an optional reference style spec
| Name | Type | Req | Description |
|---|---|---|---|
| lumen_program | string | yes | Lumen binary name; must be in allow_programs |
| output | string | yes | Output file name (.png), written under the state dir |
| preset | string | yes | Lumen style preset name (see lumen style_list) |
| reference | string | – | Optional art target whose style spec the output is verified against |
| strength | number | – | Grade strength (default 1.0) |
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
binary_overview ~32
Program identity, memory map, and inventory counts
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
capture_process ~44
Run an allowlisted command confined, capturing output, exit, timing, and hashes
| Name | Type | Req | Description |
|---|---|---|---|
| command | array | yes | argv; the program must be allowlisted by name in config |
No output schema declared.
No examples provided.
compare_artifacts ~35
Compare two artifacts: identity, sizes, and byte equality
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | – |
| b | string | yes | – |
No output schema declared.
No examples provided.
export_evidence_bundle ~27
Package evidence envelopes into a digest-sealed bundle
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No output schema declared.
No examples provided.
inspect_android_apk ~46
Static APK inventory: ZIP contents, contents classes, and the binary-XML manifest (package, permissions, components)
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
inspect_artifact ~33
File identity and classification, or a bounded directory inventory
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
inspect_asar ~37
ASAR archive inventory: entries, sizes, offsets, unpacked flags
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
inspect_binary_layout ~34
Container layout and mitigation candidates, read directly (no engine)
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
inspect_evm_bytecode ~55
Offline EVM bytecode: dispatcher scan and inferred function selectors
| Name | Type | Req | Description |
|---|---|---|---|
| bytecode | string | – | Hex bytecode, optional 0x prefix |
| target | string | – | Or a file under a target root |
No output schema declared.
No examples provided.
inspect_firmware ~42
Firmware inspection: header/format detection, embedded-filesystem signature scan, entropy profile (no extraction)
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
inspect_managed_assembly ~43
.NET metadata inventory: identity, types, methods, P/Invoke, signature digests
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
inspect_source_map ~64
Source-map v3 parsing: sources, sourcesContent presence, segments, and generated-to-original position mapping
| Name | Type | Req | Description |
|---|---|---|---|
| generated_column | integer | – | – |
| generated_line | integer | – | – |
| target | string | yes | Path to a .map file under a configured target root |
No output schema declared.
No examples provided.
inspect_web_capture ~34
HAR capture reading: request/response inventory and payload exposure
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
list_functions ~28
Function inventory with classifications and signatures
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
list_names ~30
Symbol inventory: addresses, names, types
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
list_strings ~27
Defined-string inventory with addresses
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
observe_browser ~37
Chromium-headless page observation: title, meta, script, link, and form inventory from the serialized DOM
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
remap_palette ~112
Native deterministic palette remap of an image (nearest or exact) to a supplied palette or another asset's measured palette
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | Default nearest |
| output | string | yes | Output file name (.png), written under the state dir |
| palette | array | – | #RRGGBB entries (1..=256); mutually exclusive with palette_from |
| palette_from | string | – | Art target whose measured palette to use |
| target | string | yes | Path under a configured target root |
No output schema declared.
No examples provided.
search_inventory ~33
Substring search across functions, symbols, and strings
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| target | string | yes | – |
No output schema declared.
No examples provided.
session_info ~18
Server identity, catalog digest, and tool availability
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_evidence_bundle ~29
Verify a bundle's digest and re-hash its subjects
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Fathom MCP server?
Fathom ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 31e6127f1c9fdeccf43bb95073e201ecc6f6959caab64c05a7ba915f5e8bbe19; the commands to do that are on this page. If it does not match, do not open it.
mcpb · linux-x64
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
31e6127f1c9fdeccf43bb95073e201ecc6f6959caab64c05a7ba915f5e8bbe19
macOS / Linux
echo "31e6127f1c9fdeccf43bb95073e201ecc6f6959caab64c05a7ba915f5e8bbe19 fathom-mcp-0.1.1-linux-x64.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\fathom-mcp-0.1.1-linux-x64.mcpb).Hash -eq "31e6127f1c9fdeccf43bb95073e201ecc6f6959caab64c05a7ba915f5e8bbe19"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Fathom MCP server?
Fathom is an MCP server listed in the public MCP registry as ai.qompass/fathom. Reverse-engineering tools for agents over MCP/A2A, with evidence-carrying findings. This page covers its MCPB bundle (https://github.com/qompassai/fathom/releases/download/v0.1.1/fathom-mcp-0.1.1-linux-x64.mcpb).
Is the Fathom MCP server safe to use?
Fathom scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fathom MCP server expose?
Fathom exposes 25 tools: analyze_art_style, analyze_function, analyze_javascript_application, apply_style_via_lumen, binary_overview, and 20 more. Their descriptions and schemas cost roughly 1,115 tokens of context every time the server is loaded.
What licence is the Fathom MCP server under?
Fathom declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.