mcpbeat Sign in

FX Context MCP Server

by coco-pier Your server? Claim it
answering

FX Context is answering right now. Last checked 11 min ago. It exposes 6 tools.

FX macro context: CPI, NFP, PCE, ISM PMIs, Fed, ECB, BoE, BoJ, historical analogs, FX reactions.

Uptime history 54 days of history · worst day 92%
54 days agonow
100.0%
Uptime 24h
91 of 91 checks
6
Tools
read from the server
476 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 71

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 September 2026. No other catalogue keeps this.

10 Oct 5 tool descriptions were rewritten8 times that day get_event_context, get_historical_analogs, get_historical_reaction_context and 2 more
10 Oct 4 tools changed the parameters they ask for5 times that day get_event_context, get_historical_analogs, get_historical_reaction_context and 1 more
10 Oct a tool changed version2 times that day
8 Oct 3 tool descriptions were rewritten get_historical_analogs, get_historical_reaction_context, get_upcoming_risks
8 Oct 3 tools changed the parameters they ask for get_historical_analogs, get_historical_reaction_context, get_upcoming_risks
8 Oct a tool changed version
3 Oct a tool description was rewritten get_event_context
3 Oct a tool changed the parameters it asks for get_event_context
3 Oct a tool changed version
23 Sep 3 tool descriptions were rewritten get_historical_analogs, get_market_reaction, get_upcoming_risks
and 48 more, back to 19 September 2026

Nothing serious here today

Today is the operative word: we check FX Context every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add fx-context --transport http https://fx.coco-pier.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://fx.coco-pier.com/mcp
~/.codex/config.toml
[mcp_servers.fx-context]
url = "https://fx.coco-pier.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fx-context": {
      "url": "https://fx.coco-pier.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "fx-context": {
      "type": "http",
      "url": "https://fx.coco-pier.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

historical
get_historical_analogs
Find and return individual historical macroeconomic releases whose surprise profiles are most similar to a selected target event. Use this CASE-RETRIEVAL tool when the user wants to identify, rank, inspect, or compare specific historical analog events. It returns the matched events themselves, including event identity, similarity characteristics, surprise profile, and each event's observed post-release reaction. Supported event types: US_CPI and US_NONFARM_PAYROLLS across EURUSD, GBPUSD, and USDJPY. US_PCE is recognized but not yet publicly available: the historical PCE calibration corpus currently has too few usable periods, and a request for US_PCE returns a structured INSUFFICIENT_HISTORICAL_CALIBRATION error (with usable/required event counts) instead of analog results until the corpus grows. ISM is not currently available here: US_ISM_MANUFACTURING and US_ISM_SERVICES have no verified pre-release consensus yet, so they return INSUFFICIENT_HISTORICAL_CALIBRATION rather than analogs. For ISM, use get_event_context for actuals and get_market_reaction for price moves. Similarity methodology is event-specific: US_CPI uses headline/core surprise distance; US_NONFARM_PAYROLLS uses target-relative robust scale normalization (nfp-historical-analog-v1); US_PCE (once activated) uses the same raw surprise -distance approach as US_CPI (pce-historical-analog-v1). Target period: if referencePeriod is omitted, the target is the most recent event of the requested type. Surprises are never estimated, so if that event has no verified pre-release consensus (common right after a new NFP release) the tool fails with NO_VERIFIED_PRE_RELEASE_EXPECTATION. The error details include targetReferencePeriod, latestReleasedPeriod, latestPeriodWithVerifiedExpectation and a hint; to analyze that prior period, retry with referencePeriod=YYYY-MM. Tell the user the newest release could not be analyzed rather than presenting the prior period as the latest. Every "cannot compute" error has the same shape: "CODE: reason [hint] details={json}", where the JSON always contains code, eventType and hint. Do NOT use this tool when the user's primary question is about aggregate behavior across the analog sample; use get_historical_reaction_context instead. The results are historical observations only and do not predict future price direction or provide trading recommendations.
get_historical_reaction_context
Summarize the aggregate post-event reaction pattern across historical macroeconomic events similar to a selected target release. Use this AGGREGATE-PATTERN tool when the user wants to understand what the historical analog sample collectively showed rather than inspect individual analog events. It summarizes historical outcomes using statistics and behavioral patterns across standardized post-event windows (M5, M15, H1, H4, H24) such as mean, median, quantiles, directional consistency, reaction-path classification (e.g. IMMEDIATE_CONTINUATION, INITIAL_REVERSAL, FADE, DELAYED_REACTION), persistence, and sample-size-based confidence. Supported event types: US_CPI and US_NONFARM_PAYROLLS across EURUSD, GBPUSD, and USDJPY. ISM is not currently available here: US_ISM_MANUFACTURING and US_ISM_SERVICES have no verified pre-release consensus yet, so they return a structured INSUFFICIENT_HISTORICAL_CALIBRATION error rather than aggregate statistics. Similarity methodology is event-specific: US_CPI uses headline/core surprise distance; US_NONFARM_PAYROLLS uses target-relative robust scale normalization (nfp-historical-analog-v1). Target period: if referencePeriod is omitted, the target is the most recent event of the requested type. Surprises are never estimated, so if that event has no verified pre-release consensus (common right after a new NFP release) the tool fails with NO_VERIFIED_PRE_RELEASE_EXPECTATION. The error details include targetReferencePeriod, latestReleasedPeriod, latestPeriodWithVerifiedExpectation and a hint; to analyze that prior period, retry with referencePeriod=YYYY-MM. Tell the user the newest release could not be analyzed rather than presenting the prior period as the latest. Every "cannot compute" error has the same shape: "CODE: reason [hint] details={json}", where the JSON always contains code, eventType and hint. Do NOT use this tool when the user's primary goal is to identify, rank, enumerate, or inspect specific historical analog events. For individual historical cases, use get_historical_analogs. When the user asks for both specific cases and collective pattern analysis, invoke both tools. The results are deterministic empirical observations only and do not predict future prices or provide trading recommendations.
central
get_central_bank_changes
Compare a central bank monetary-policy statement with its immediately preceding comparable statement and return the material changes in policy language, economic assessment, risk balance, and forward guidance. Specify a central bank such as FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). Optionally specify currentStatementDate in YYYY-MM-DD format to compare a historical statement. If the date is omitted, the latest available statement is compared with the previous one. Returns structured, source-grounded policy changes including direction, materiality, and previous/current evidence. This tool does not provide trading recommendations or predict market movements.
event
get_event_context
Get the official actual values, pre-release market consensus, and surprise for a specific U.S. macro data release: CPI (US_CPI), Nonfarm Payrolls / jobs report (US_NONFARM_PAYROLLS), PCE inflation (US_PCE), or the ISM Manufacturing / Services PMI (US_ISM_MANUFACTURING / US_ISM_SERVICES). WHEN TO CALL: whenever the user asks what a release printed or how it compared with expectations, even if they do not mention FX Context. Do not answer these from memory; recent releases are not in your training data. Examples: - "What's the latest US PCE?" -> US_PCE - "Was core PCE hotter than expected?" -> US_PCE - "Did CPI beat expectations?" -> US_CPI - "What was the latest NFP?" / "How many jobs were added last month?" -> US_NONFARM_PAYROLLS - "Give me the latest US inflation release." -> US_CPI and/or US_PCE - "What's the latest ISM Manufacturing PMI?" -> US_ISM_MANUFACTURING - "Did ISM Services beat expectations?" -> US_ISM_SERVICES - "What were the actual and consensus values?" / "What was the surprise?" -> the release under discussion Omit referencePeriod for the latest release. For a specific release, pass the month the data covers (YYYY-MM), not the month it was published. WHEN NOT TO CALL: general or educational questions that need no specific release data, e.g. "What is PCE?", "What does NFP stand for?", "Why does CPI matter for FX?", "Explain inflation.", "What is the difference between CPI and PCE?". Use get_upcoming_risks for upcoming release dates, get_market_reaction for price moves after a release, and get_central_bank_changes for central-bank decisions. RESULT: per-metric official actuals (headline/core, MoM/YoY; ISM: headline PMI index) with publisher provenance; when valid, pre-release consensus and a deterministic actual-minus-consensus surprise. Each observation has consensusStatus (AVAILABLE, NOT_FOUND, NOT_CAPTURED, NOT_AVAILABLE, EXCLUDED_POST_RELEASE, NOT_APPLICABLE) explaining any missing consensus, and revisionStatus (REVISED, UNCHANGED, NOT_CAPTURED). Consensus is valid only when capturedAt is before releaseCutoffAt. ISM (US_ISM_MANUFACTURING, US_ISM_SERVICES) currently returns official actuals only: consensusStatus is NOT_CAPTURED and no surprise is computed, so an ISM beat/miss question cannot be answered from this tool yet. Never treat missing consensus or surprise as zero. Official actuals and third-party consensus keep separate source provenance. No trading recommendations or market-direction predictions.
market
get_market_reaction
Retrieve deterministic post-event market reaction metrics for an economic release or monetary policy statement. Specify the targetType, such as US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), US_ISM_MANUFACTURING (alias ISM_MANUFACTURING), US_ISM_SERVICES (alias ISM_SERVICES), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). Optionally specify dateOrPeriod: - For US_CPI, US_PCE, US_NONFARM_PAYROLLS, and the ISM PMIs: reference period in YYYY-MM format (e.g. 2024-07). If omitted, the latest event is resolved. - For FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND, or BANK_OF_JAPAN: statement date in YYYY-MM-DD format (e.g. 2024-08-01). If omitted, the latest statement is resolved. Optionally specify instrument: EURUSD, GBPUSD, or USDJPY (defaults to EURUSD). Returns deterministic price action metrics across 5 standardized post-event windows (M5, M15, H1, H4, H24) including startPrice, endPrice, returnPct, high, low, maxUpMovePct, maxDownMovePct, and rangePct. All calculations are strictly deterministic and mathematical. This tool does not provide trading recommendations or predictive signals.
upcoming
get_upcoming_risks
Retrieve known scheduled macroeconomic and central-bank risks that may affect a supported FX instrument within a future time window. Use this tool when the user asks what could move EURUSD, GBPUSD, or USDJPY, what macro risks are coming up, what is happening in the next 24 hours, this week, or over the next month, what upcoming macro risks or scheduled events exist, or when the next CPI, next NFP, next PCE, next ISM, next Fed, next ECB, next BoE, or next BoJ event occurs. The supported risks are U.S. CPI releases, U.S. Nonfarm Payrolls releases, U.S. PCE inflation releases, ISM Manufacturing and Services PMI releases, Federal Reserve monetary-policy decisions, ECB monetary-policy decisions, Bank of England monetary-policy decisions, and Bank of Japan monetary-policy decisions. The horizon can extend up to 720 hours (30 days). scheduleCoverage reports, for each supported event type, the latest known scheduled date and whether the known calendar covers the whole window. If scheduleCoverageComplete is false, some event types may have additional events in the window that are not yet known; say so instead of treating the list as complete. Results are based on official release calendars and contain scheduled events only. This tool does not predict market direction, include unscheduled news, or provide trading recommendations. If no supported scheduled event exists within the requested horizon, an empty risk list is returned.

Endpoints

URLTransportStateLatencyChecked
https://fx.coco-pier.com/mcp streamable-http answering 450 ms 11 min ago

Alternatives to FX Context

same job, measured the same way
Insightiq
by ravi-p-k-1

Look up real FRED (Federal Reserve Economic Data) series and historical observations.

41 installs/wk local only
G
Git Archaeologist
by engrmaziz

Trace code history, commit reasoning, and PR context directly from Git logs.

56 installs/wk local only
CurrencyCore
by currencycore

Live FX rates, conversion, IMF PPP, and historical currency analytics.

14 tools answering
Ikuna
by robertohanas

Read workspace context and activity from the running Ikuna macOS app, with app-managed permissions.

38 installs/wk local only
Januscope
by giancarloerra

Local MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.

60 installs/wk local only
D
DatoQA — Historical Exchange Rates
by workers-bhazarstudio-datoqa

Historical reference FX and dated conversions across 30 currencies, with source dates and evidence.

7 tools answering
Market Intel MCP
by datakoot

Live & historical FX rates and currency conversion for AI agents. No API keys.

5 tools answering
Callejear Germany
by habanacasta88

Read-only German street search and context across 593,062 historical records.

5 tools answering

FX Context — questions

Answers built from our own checks of this server.

What can FX Context do?
It exposes 6 tools, read directly from the server on our last check. Among them: get_central_bank_changes, get_event_context, get_historical_analogs, get_historical_reaction_context, get_market_reaction, get_upcoming_risks. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is FX Context working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 476 ms. The bar chart above shows every period we have measured.
How do I connect FX Context?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FX Context need an API key?
No. FX Context completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FX Context?
It answers our handshake in 476 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.