Is Fred MCP Server safe to use?

Fred MCP Server has an HVTrust score of 71.3/100 (Grade B), ranked #307 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Fred MCP Server?

Fred MCP Server scores 71.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 122 GitHub stars and is categorized under MCP Servers.

Fred MCP Server

stefanoamorelli/fred-mcp-server

Open-source FRED MCP Server (Federal Reserve Economic Data)

MCP Servers TypeScript Listed AGPL-3.0

Is Fred MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10

Provenance Attested

Signed commits 48%

Last push 35d ago

Compare Fred MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Fred MCP Server scores 71.3/100 (Grade B), ranked #307 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 48% of recent commits are signed; last pushed 2026-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Fred MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Fred MCP Server’s 71.3.

Where the 71.3 comes from

HVTrust dimensions vs the MCP Servers average

71.3 / 100 · 100.0% confidence

Fred MCP Server MCP Servers average (775 agents)

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

16.8 / 25

6.5 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.2 / 17

1.0 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.7 / 20

2.4 below avg 12.1

AdoptionLog-scaled stars · package downloads

8.6 / 20

1.4 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-24

Rank Moved

Rank dropped 22 spots (#285 → #307)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.

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 35 days ago. Fresh activity helps separate stable projects from stale ones.

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

40.2

Activity sub-score · out of 100

#183

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 B 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

122

Forks

Last Push

2026-08-22

35 days ago

Commits (4 wk)

Downloads (7d)

455

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #310

Analysis

Activity Inputs

40.2 / 100

StarsRepository reach

12.5 / 30

FreshnessLast push recency

20.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.5 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

48%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Fred MCP Server

Fred MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Fred MCP Server publish package provenance?

Yes. Fred MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Fred MCP Server have an OpenSSF Scorecard?

Fred MCP Server has an OpenSSF Scorecard score of 5.5/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 Fred MCP Server actively maintained?

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

What license does Fred MCP Server use?

Fred MCP Server ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Fred MCP Server's commits signed?

48% of the last 100 commits to Fred 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

Fred MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

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 Fred 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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-03

Provenance Added

Package provenance attestation detected

2026-08-20

Activity Resumed

Activity resumed

2026-08-14

Activity Went Stale

No commits for 90 days

Maintain Fred MCP Server?

For maintainers

HVTrust scores Fred 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

2026-09-24

Rank Moved

Rank dropped 22 spots (#285 → #307)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 714 spots (#999 → #285)

2026-09-23

HVTrust Changed

HVTrust up 47.4pts (24.9 → 72.3)

2026-09-22

Newly Listed

First tracked at rank #999

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank dropped 52 spots (#209 → #261)

2026-09-19

Activity Score Changed

Activity score down 8pts (55 → 47)

2026-09-07

Rank Moved

Rank dropped 13 spots (#167 → #180)

2026-09-05

Rank Moved

Rank dropped 35 spots (#131 → #166)

2026-09-04

Grade Changed

Trust grade C → B

2026-09-04

Rank Moved

Rank rose 603 spots (#734 → #131)

2026-09-04

HVTrust Changed

HVTrust up 26.3pts (50.7 → 77.0)

2026-09-03

Provenance Added

Package provenance attestation detected

2026-09-03

Grade Changed

Trust grade D → C

2026-09-03

Rank Moved

Rank rose 212 spots (#946 → #734)

2026-09-03

HVTrust Changed

HVTrust up 9.4pts (41.3 → 50.7)

2026-09-02

Rank Moved

Rank dropped 50 spots (#896 → #946)

2026-09-01

Scorecard Added

OSSF Scorecard: 5.5/10

2026-09-01

Rank Moved

Rank rose 298 spots (#1194 → #896)

2026-09-01

HVTrust Changed

HVTrust up 19.1pts (22.2 → 41.3)

2026-08-31

Rank Moved

Rank dropped 27 spots (#1167 → #1194)

2026-08-30

Rank Moved

Rank dropped 36 spots (#1131 → #1167)

2026-08-29

Rank Moved

Rank dropped 34 spots (#1097 → #1131)

2026-08-28

Rank Moved

Rank dropped 33 spots (#1064 → #1097)

2026-08-27

Rank Moved

Rank dropped 19 spots (#1045 → #1064)

2026-08-26

Rank Moved

Rank dropped 78 spots (#967 → #1045)

2026-08-24

Rank Moved

Rank dropped 12 spots (#949 → #961)

2026-08-22

Rank Moved

Rank rose 17 spots (#970 → #953)

2026-08-20

Activity Resumed

Activity resumed

2026-08-20

Rank Moved

Rank rose 199 spots (#1175 → #976)

2026-08-20

HVTrust Changed

HVTrust up 4.2pts (18.1 → 22.3)

2026-08-20

Activity Score Changed

Activity score up 26pts (31 → 58)

2026-08-16

Rank Moved

Rank dropped 23 spots (#1148 → #1171)

2026-08-14

Activity Went Stale

No commits for 90 days

2026-08-10

Rank Moved

Rank dropped 65 spots (#1082 → #1147)

2026-08-08

Newly Listed

First tracked at rank #1074

GitHub → npm: fred-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/fred-mcp-server.svg)](https://hvtracker.net/agents/fred-mcp-server)
            
HTML:
            <a href="https://hvtracker.net/agents/fred-mcp-server"><img src="https://hvtracker.net/badge/fred-mcp-server.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