Skip to content
MacroDataAPI logo

MacroDataAPI MCP server

Which MCP servers are MacroDataAPI's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-02

← Back to MacroDataAPI

Whose server it is
  • Registry namecom.macrodataapi/macrodataverified in the MCP registry

The registry name sits under macrodataapi.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-02
  • Stateanswerschecked 2026-11-02
  • Tools10
  • Server calls itselfmacrodataapi
  • Server version1.30.0
  • Protocol version2025-06-18

On 2026-11-02 the server answered initialize and tools/list without a sign-in. First answer in 191 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • create_free_api_key change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 6 of 10 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-11-02
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer536 ms
  • Space in an agent's context≈ 1,075 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 90 of 100
  • Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 6 of 10

What an agent can do with it

  • not sure · backtest models on data as it was known
  • not sure · pull CPI and payrolls at release time
  • can do · track policy rates and yield curves

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_free_api_key

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-11-02
  • list_capabilities

    What this server offers, prices and the first calls to make. No key needed.

  • create_free_api_key

    Create a FREE MacroDataAPI key (no signup). Returned once; add it to the server's X-API-Key header.

  • macro_search_series

    Search the series catalog: ids, units, frequency, latest period and next release.

  • macro_latest

    Latest print of a series with previous value, changes, release time and next release.

  • macro_history

    History of a series (Pro). With as_of, values are as they stood on that date (point-in-time).

  • macro_vintages

    Every revision of one period of a series (Pro): initial print and later values with vintage dates.

  • macro_calendar

    Scheduled data releases for the next N days, with the series each updates.

  • macro_latest_releases

    The most recent releases observed, with headline values.

  • macro_policy_rates

    Current policy rates with the last decision date and next meeting.

  • macro_yield_curve

    Daily par yield curve with the previous session, change per tenor and 2s10s spread.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "macrodata": {
      "type": "http",
      "url": "https://macrodataapi.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http macrodataapi https://macrodataapi.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://macrodataapi.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.