Skip to main content
Glama
mike-whypred

FRED API MCP Server

by mike-whypred

Related Servers

Alternatives to FRED API MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the Federal Reserve Economic Data (FRED) API, providing access to over 800,000 economic time series like GDP and unemployment. It enables AI agents to search for data, retrieve metadata, and fetch historical observations directly from the St. Louis Fed.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables browsing, searching, and retrieving FRED economic data (800k+ indicators) through LM Studio plugins or MCP, with units/frequency conversion. Supports natural language queries for series like GDP and UNRATE.
      Apache 2.0
    • A
      license
      C
      quality
      D
      maintenance
      Provides access to economic data from the Federal Reserve Bank of St. Louis (FRED) through the Model Context Protocol, allowing AI assistants to retrieve economic time series data directly.
      1
      6
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables searching and retrieving economic data from the Federal Reserve Economic Data (FRED) API, including time series, categories, releases, and popular indicators.
      7
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Federal Reserve Economic Data (FRED) through Claude and other LLM clients, enabling users to search for, retrieve, and visualize economic indicators like GDP, employment, and inflation data.
      8
      -
    • F
      license
      A
      quality
      D
      maintenance
      A local MCP server that gives Claude and other MCP clients access to Federal Reserve Economic Data (FRED) — 800,000+ economic time series covering GDP, inflation, employment, interest rates, and more.
      3
      2
      -

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of ambiguity or misselection. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    The single tool name follows a clear snake_case verb_noun convention. With only one tool, the naming is trivially consistent.

    Tool Count2/5

    One tool is too few for a server claiming to represent the FRED API, which has a broad range of endpoints. The apparent scope far exceeds what a single tool can cover.

    Completeness1/5

    The FRED API supports many resource types (series, categories, releases, sources, etc.) beyond just fetching observations. This server only exposes one observation endpoint, leaving the surface severely incomplete for the stated purpose.