Skip to main content
Glama

Nber Macrohistory

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

NBER Macrohistory Database — the National Bureau of Economic Research's

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.4% over 21 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-nber-macrohistory
GitHub Stars
0
Server Listing
nber-macrohistory

TDQS

A3.9/5.0

Scored across 38 tools

Disambiguation2/5

The two NBER tools are clearly distinct, but the wider 38-tool set contains several overlapping meta-routing tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and multiple company/financial lookup tools whose boundaries blur. An agent could easily misselect among the Pipeworx router variants or between entity_profile, company_facts, compare_entities, and recent_changes.

Naming Consistency4/5

Tool names are consistently snake_case throughout, which is the main naming convention that matters. There is some variation in pattern (verb_noun like list_subscriptions and resolve_entity vs noun phrases like entity_profile and company_facts), but it remains readable and predictable enough.

Tool Count2/5

For a server named Nber Macrohistory, only two tools (nber_macrohistory_list_series and nber_macrohistory_series) actually serve that domain. The other 36 tools are unrelated Pipeworx gateway/meta/market tools, making 38 tools far too many for the apparent scope.

Completeness3/5

The NBER surface covers category listing and single-series retrieval, which is the core read path for the archive. However, there is no title-based search, no cross-category discovery, no bulk export, and no metadata-only lookup, so notable gaps remain for a historical data research workflow.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 38 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observednber_macrohistory_list_series
    • First observednber_macrohistory_series
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • FRED MCP Server

    shawndrake2
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides access to over 800,000 economic time series from the Federal Reserve Bank of St. Louis, including data on GDP, inflation, and employment. It enables users to search for, retrieve, and analyze various economic indicators and state-level statistics.
    1
    -
  • Market Intelligence MCP by BullrunData

    Market Intelligence MCPofficial

    BullrunData
    A
    license
    A
    quality
    C
    maintenance
    Recession probability, capital rotation, macro cascade analysis, and real-time economic data for Claude, ChatGPT, Cursor, and any MCP client.
    23
    32 npm
    1
    MIT

  • Federal Reserve Economic Data

    stefanoamorelli
    A
    license
    A
    quality
    A
    maintenance
    Provides access to over 800,000 economic time series from the Federal Reserve, allowing users to browse, search, and retrieve data for indicators like GDP and unemployment. It supports custom date ranges and data transformations such as percentage changes or frequency aggregations.
    3
    240 npm
    125
    AGPL 3.0

  • FeedOracle Macro MCP

    feedoracle
    F
    license
    Not graded
    quality
    D
    maintenance
    Macro economic intelligence MCP — 13 tools powered by 86 FRED series + ECB data covering Fed rates, inflation (CPI/PCE), yield curve, GDP, recession probability, and regime classification. Every response ES256K signed.
    1
    -
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources