No user-submitted related servers found.
Scored across 33 tools
Most tools are scoped to a distinct FRED entity, but the many tag-related variants (fred_tags, fred_related_tags, fred_series_tags, fred_series_search_tags, fred_series_search_related_tags, fred_category_tags, fred_release_tags) overlap in purpose and could easily be misselected. Singular/plural pairs like fred_releases/fred_release and fred_releases_dates/fred_release_dates also create avoidable ambiguity.
The snake_case fred_<entity>_<detail> and geofred_<detail> patterns are mostly consistent and readable. Minor inconsistencies exist: fred_related_tags doesn't follow the same entity-action structure, and plural/singular pairs like fred_sources vs fred_source alternate between list-all and get-one without a uniform prefix like 'list_' or 'get_'.
At 33 tools, this is well beyond the comfortable MCP scope and would overwhelm an agent trying to pick the right endpoint. While each tool maps to a real FRED API endpoint, several could be consolidated, making the surface heavier than necessary for agent use.
The server covers the full FRED domain: categories, releases, series, observations, sources, tags, updates, vintage dates, and GeoFRED regional data. Since FRED is a read-only data API, the absence of create/update/delete operations is appropriate, and there are no obvious dead-end workflows.