Home / MCP registry index / io.github.fxmacrodata/fxmacrodata
FXMacroData
io.github.fxmacrodata/fxmacrodata in the official MCP registry.
Endpoint https://fxmacrodata.com/mcp. Source: github.com/fxmacrodata/fxmacrodata.
The registry describes it as: Macroeconomic and FX time-series data for AI agents: indicators, calendars, COT, forex, commodities.
We read its 56 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ping mcp_capabilities mcp_auth_guide subscribe_for_mcp_access data_catalogue risk_sentiment risk_sentiment_changes macro_news release_calendar calendar_snapshot calendar_event_versions calendar_archive_coverage release_calendar_visual_artifact event_predictions latest_announcements announcement_changes press_releases macro_factor fx_reference_sources fx_reference_universe fx_intraday_reference_rates rate_curve rate_differentials latest_commodities forex seasonality indicator_query plot_visual_artifact indicator_visual_artifact forex_visual_artifact commodities_visual_artifact cot_visual_artifact policy_rate_differential_visual_artifact macro_briefing_task indicator_intel_task pair_intel_task macro_heatmap_task policy_scenario_modeler_task macro_war_room_task event_impact_replay_task quant_scenario_lab_task known_at_time_task macro_regime_classifier_task release_risk_score_task portfolio_risk_engine_task fx_trade_setup_task fx_backtest_task macro_research_pack_task prediction_coverage market_sessions cot_data commodities positioning native_history financial_prices official_dataset_family
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-fxmacrodata-fxmacrodata)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.