Is Fanout MCP safe to use?

Fanout MCP has an HVTrust score of 34.7/100 (Grade D), ranked #1247 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Fanout MCP?

Fanout MCP scores 34.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

Fanout MCP

houtini-ai/fanout-mcp

A Query fan-out analyser for AI Search

MCP Servers TypeScript Listed Apache-2.0

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

OSSF Scorecard 1.6 / 10

Provenance None

Signed commits 4%

Last push 163d ago

Compare Fanout MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

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

How Fanout MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Fanout MCP’s 34.7.

Where the 34.7 comes from

HVTrust dimensions vs the MCP Servers average

34.7 / 100 · 100.0% confidence

Fanout MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

2.2 / 25

8.1 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

9.9 / 17

2.3 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

1.1 / 20

11.0 below avg 12.1

AdoptionLog-scaled stars · package downloads

5.7 / 20

1.5 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: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Scorecard Added

OSSF Scorecard: 1.6/10

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.6/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 163 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Fanout MCP View MCP Servers Report missing data

12.0

Activity sub-score · out of 100

#745

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-04-16

163 days ago

Commits (4 wk)

Downloads (7d)

188

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #1247

Analysis

Activity Inputs

12.0 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

2.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

2.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.6 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0

Common questions about Fanout MCP

Public trust evidence for Fanout MCP 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 Fanout MCP publish package provenance?

No published build provenance is currently detected for Fanout MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Fanout MCP have an OpenSSF Scorecard?

Fanout MCP has an OpenSSF Scorecard score of 1.6/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 Fanout MCP actively maintained?

Slowing down. Last push was 163 days ago — keep an eye on whether activity resumes.

What license does Fanout MCP use?

Fanout MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Fanout MCP's commits signed?

3% of the last 100 commits to Fanout MCP 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

Fanout MCP 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.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 Fanout MCP'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: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Fanout MCP?

For maintainers

HVTrust scores Fanout MCP 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

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Scorecard Added

OSSF Scorecard: 1.6/10

2026-09-23

Rank Moved

Rank rose 82 spots (#1323 → #1241)

2026-09-23

HVTrust Changed

HVTrust up 29.1pts (6.0 → 35.1)

2026-09-22

Newly Listed

First tracked at rank #1323

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Rank Moved

Rank dropped 12 spots (#1274 → #1286)

2026-09-04

Rank Moved

Rank dropped 15 spots (#1259 → #1274)

2026-09-03

Rank Moved

Rank dropped 32 spots (#1227 → #1259)

2026-09-02

Rank Moved

Rank rose 80 spots (#1307 → #1227)

2026-09-02

HVTrust Changed

HVTrust up 8.7pts (15.0 → 23.7)

2026-08-26

Rank Moved

Rank dropped 18 spots (#1259 → #1277)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1234 → #1260)

2026-08-10

Rank Moved

Rank dropped 76 spots (#1154 → #1230)

2026-08-08

Newly Listed

First tracked at rank #1153

GitHub → npm: @houtini/fanout-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/fanout-mcp.svg)](https://hvtracker.net/agents/fanout-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/fanout-mcp"><img src="https://hvtracker.net/badge/fanout-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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