MCP.Market

Ferric Fred MCP server

by ojhermann-org·io.github.ojhermann-org/ferric-fred-mcp·v0.3.11
No reviews yet

MCP server for FRED (Federal Reserve Economic Data): full read API plus GeoFRED, 34 tools.

C63/100grade C
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
C63/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Ferric Fred yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Ferric Fred tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 36 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 63/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Ferric Fred compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
63/100
higher than 18% of 48,255 servers

Install Ferric Fred in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Ferric Fred repository's README, as published. We do not edit it. Read it on GitHub

ferric-fred

A strongly-typed Rust client for FRED — the Federal Reserve Economic Data service from the Federal Reserve Bank of St. Louis — plus a CLI (with TUI charts) and an MCP server built on top of it.

ferric (iron oxide → rust) + FRED. Iron-clad, typed access to economic data.

Workspace

A Cargo workspace of three crates — each with its own README (the crates.io / docs.rs landing page) that carries the full usage detail:

Published versions (these badges are the source of truth — the crates version independently, so they can drift out of lockstep):

Consumers depend on the library by workspace path, so a breaking change in the library cannot compile-pass its consumers without updating them — that compile-time coupling is the primary "stay in sync" guarantee (versions are managed on top; see the ADRs).

What it covers

The library wraps all of FRED's read endpoints — series and observations (including ALFRED point-in-time / vintage data via a real-time window), search, categories, releases (including the nested release-table tree, with optional inline observation values), sources, and tags — plus the GeoFRED / Maps API (regional data and the geographic shape files to map it, ADR-0025) — behind ergonomic builders, with newtype identifiers, typed enums for FRED's closed value sets, a non-panicking error taxonomy, and auto-pagination (Paginate::send_all walks an endpoint to exhaustion, Paginate::stream yields lazily; --all on the CLI). See ADR-0020 and ADR-0021.

GeoFRED support spans the library, CLI (fred geofred), and MCP (getregionaldata, getseriesdata, getseriesgroup) layers. The one exception is the geographic shapes/file endpoint, which is library/CLI-only — a large projected-GeoJSON blob is poor ergonomics for an MCP tool caller (ADR-0025).

Pick an entry point:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Ferric Fred: common questions

Is Ferric Fred MCP server safe?
With care: it is graded C, so read the findings first (63/100). Read the Ferric Fred safety report
Does Ferric Fred need an API key?
Yes. The registry entry asks for FRED_API_KEY.
Is Ferric Fred maintained?
The last commit was 76 days ago (2026-08-20). The latest release is v0.3.11.