updated 2026-09-26 06:32 UTC

Fathom MCP Server

agencyenterprise/fathom-mcp-server

An mcp server built for fathom and works in claude.

MCP Servers TypeScript Listed MIT

Is Fathom MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.4 / 10
Provenance None
Signed commits 25%
Last push 152d ago
Compare Fathom MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Fathom MCP Server scores 33.3/100 (Grade D), ranked #1265 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.4/10; 25% of recent commits are signed; last pushed 2026-04-27. Every point is earned from checkable signals — never paid placement. How scoring works →

How Fathom MCP Server compares in MCP Servers

  1. #756 MCP Explorium 33.5 +0.2
  2. #757 Banco MCP 33.3 ±0
  3. #758 Fathom MCP Server 33.3 this agent
  4. #759 N8n MCP 33.0 −0.3
  5. #760 Nanobanana MCP Server 32.7 −0.6

Bars show each HVTrust score; the tick marks Fathom MCP Server’s 33.3.

Where the 33.3 comes from

HVTrust dimensions vs the MCP Servers average

33.3 / 100 · 100.0% confidence

Fathom MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.5 / 25
4.8 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.4 / 17
0.8 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
1.9 / 20
10.2 below avg 12.1
AdoptionLog-scaled stars · package downloads
3.0 / 20
4.2 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 194 spots (#1068 → #1262)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 152 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Fathom MCP Server View MCP Servers Report missing data
16.9
Activity sub-score · out of 100
#758
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 152 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
16
Forks
14
Last Push
2026-04-27
152 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
3
Rank Change
▲1
was #1266

Analysis

Activity Inputs

16.9 / 100
StarsRepository reach
7.4 / 30
FreshnessLast push recency
3.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
5.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.4 / 10
OpenSSF Scorecard · scanned Sep 22, 2026
Signed Commits
25%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 3
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about Fathom MCP Server

Public trust evidence for Fathom MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Fathom MCP Server publish package provenance?
No published build provenance is currently detected for Fathom MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Fathom MCP Server have an OpenSSF Scorecard?
Fathom MCP Server has an OpenSSF Scorecard score of 3.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Fathom MCP Server actively maintained?
Slowing down. Last push was 152 days ago — keep an eye on whether activity resumes.
What license does Fathom MCP Server use?
Fathom MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Fathom MCP Server's commits signed?
25% of the last 100 commits to Fathom MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Fathom MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Fathom MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: Anthropic

Maintain Fathom MCP Server?

For maintainers

HVTrust scores Fathom MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 15Listed 2HVTrust 2Surface 1Scorecard 1Delisted 1MCP 1Surface 1
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 194 spots (#1068 → #1262)
2026-09-23
HVTrust Changed
HVTrust up 10.5pts (23.0 → 33.5)
2026-09-22
Newly Listed
First tracked at rank #1068
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 11 spots (#1230 → #1241)
2026-09-08
Rank Moved
Rank dropped 11 spots (#1219 → #1230)
2026-09-07
Rank Moved
Rank dropped 15 spots (#1204 → #1219)
2026-09-06
Rank Moved
Rank dropped 21 spots (#1183 → #1204)
2026-09-05
Rank Moved
Rank dropped 31 spots (#1152 → #1183)
2026-09-04
Rank Moved
Rank dropped 14 spots (#1138 → #1152)
2026-09-03
Rank Moved
Rank dropped 49 spots (#1089 → #1138)
2026-09-02
Rank Moved
Rank dropped 46 spots (#1043 → #1089)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1002 → #1043)
2026-08-31
Rank Moved
Rank dropped 33 spots (#969 → #1002)
2026-08-30
Scorecard Added
OSSF Scorecard: 3.4/10
2026-08-30
Rank Moved
Rank rose 333 spots (#1302 → #969)
2026-08-30
HVTrust Changed
HVTrust up 20.8pts (14.3 → 35.1)
2026-08-26
Rank Moved
Rank dropped 15 spots (#1276 → #1291)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1248 → #1274)
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-08-10
Rank Moved
Rank dropped 79 spots (#1171 → #1250)
2026-08-08
Newly Listed
First tracked at rank #1163
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 33.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/fathom-mcp-server.svg)](https://hvtracker.net/agents/fathom-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/fathom-mcp-server"><img src="https://hvtracker.net/badge/fathom-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON