FX Context
REMOTE · FX.COCO-PIER.COM · SCANNED SEP 28
FX macro context for CPI, NFP, PCE, Fed, ECB, BoE, BoJ, historical analogs, and FX market reactions.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1952 tokens (~325/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the FX Context MCP server?
FX Context is a hosted endpoint at https://fx.coco-pier.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · fx.coco-pier.com
claude mcp add --transport http com-coco-pier-fx-context 'https://fx.coco-pier.com/mcp'
{
"mcpServers": {
"com-coco-pier-fx-context": {
"url": "https://fx.coco-pier.com/mcp"
}
}
} {
"servers": {
"com-coco-pier-fx-context": {
"type": "http",
"url": "https://fx.coco-pier.com/mcp"
}
}
} [mcp_servers.com-coco-pier-fx-context] url = "https://fx.coco-pier.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-coco-pier-fx-context": {
"type": "remote",
"url": "https://fx.coco-pier.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-coco-pier-fx-context --url 'https://fx.coco-pier.com/mcp' --transport streamable-http
mcp_servers:
com-coco-pier-fx-context:
url: "https://fx.coco-pier.com/mcp" {
"McpServers": {
"com-coco-pier-fx-context": {
"Transport": "http",
"Url": "https://fx.coco-pier.com/mcp"
}
}
} assistant mcp add com-coco-pier-fx-context -t streamable-http -u 'https://fx.coco-pier.com/mcp'
{
"mcpServers": {
"com-coco-pier-fx-context": {
"type": "http",
"url": "https://fx.coco-pier.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Tool “get_historical_analogs” rewrote its description, which is the text the model reads security
- Tool “get_market_reaction” rewrote its description, which is the text the model reads security
- Tool “get_upcoming_risks” rewrote its description, which is the text the model reads security
- Server version: 0.6.0 → 0.7.0 functional
- “get_historical_analogs” reworded the description of “eventType” cosmetic
- “get_market_reaction” reworded the description of “dateOrPeriod” cosmetic
- “get_market_reaction” reworded the description of “targetType” cosmetic
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- Tool “get_historical_analogs” rewrote its description, which is the text the model reads security
- Tool “get_historical_reaction_context” rewrote its description, which is the text the model reads security
- Tool “get_central_bank_changes” rewrote its description, which is the text the model reads security
- Tool “get_market_reaction” rewrote its description, which is the text the model reads security
- Tool “get_upcoming_risks” rewrote its description, which is the text the model reads security
- Server version: 0.5.0 → 0.6.0 functional
- Server version: 0.4.0 → 0.5.0 functional
- Server version: 0.3.0 → 0.4.0 functional
- “get_historical_analogs” reworded the description of “eventType” cosmetic
- “get_historical_analogs” reworded the description of “referencePeriod” cosmetic
- “get_historical_reaction_context” reworded the description of “eventType” cosmetic
- “get_market_reaction” reworded the description of “dateOrPeriod” cosmetic
- “get_central_bank_changes” reworded the description of “centralBank” cosmetic
- “get_market_reaction” reworded the description of “targetType” cosmetic
- 19 Sept 26 0
- Tool “get_market_reaction” rewrote its description, which is the text the model reads security
- Tool “get_upcoming_risks” rewrote its description, which is the text the model reads security
- Tool “get_event_context” rewrote its description, which is the text the model reads security
- Tool “get_historical_analogs” rewrote its description, which is the text the model reads security
- Tool “get_historical_reaction_context” rewrote its description, which is the text the model reads security
- Schema quality: 221 → 286 ▼ functional
- Schema quality: 221 → 275 ▼ functional
- Schema quality: 221 → 266 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.2.1 → 0.3.0 functional
- Server version: 0.1.0 → 0.2.1 functional
- “get_historical_analogs” reworded the description of “instrument” cosmetic
- “get_historical_reaction_context” reworded the description of “instrument” cosmetic
- “get_market_reaction” reworded the description of “instrument” cosmetic
- “get_upcoming_risks” reworded the description of “instrument” cosmetic
- “get_event_context” reworded the description of “eventType” cosmetic
- “get_historical_analogs” reworded the description of “maxAnalogs” cosmetic
- “get_historical_reaction_context” reworded the description of “limit” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://fx.coco-pier.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=coco-pier.com | CN=YE1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 533942732615c2b4f3412f96361aed8a43f |
| SANs: *.coco-pier.com, coco-pier.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fx.coco-pier.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| coco-pier.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fx.coco-pier.com/mcp | Verified | 200 | |
| http (plaintext) | http://fx.coco-pier.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_central_bank_changes ~225
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.
| Name | Type | Req | Description |
|---|---|---|---|
| centralBank | string | yes | Canonical central bank identifier: FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). |
| currentStatementDate | string | – | Optional publication date in YYYY-MM-DD format (e.g. 2024-07-31). If omitted, the latest available statement is compared with the previous one. |
| Name | Type | Req | Description |
|---|---|---|---|
| centralBank | string | yes | – |
| changes | array | yes | – |
| currentPolicyAction | string | yes | – |
| currentPolicyBias | string | yes | – |
| currentSourceUri | string | yes | – |
| currentStatementDate | string | yes | – |
| currentStatementId | string | yes | – |
| degraded | boolean | – | – |
| discardedChangeCount | integer | – | – |
| freshness | object | – | – |
| overallShift | string | yes | – |
| previousSourceUri | string | yes | – |
| previousStatementDate | string | yes | – |
| previousStatementId | string | yes | – |
No examples provided.
get_event_context ~240
Retrieve source-grounded event context for supported U.S. macro releases including US_CPI, US_NONFARM_PAYROLLS, and US_PCE. ALWAYS invoke this tool instead of relying on internal training data or memory whenever the user asks about US CPI, US Nonfarm Payrolls (NFP), or US PCE inflation (latest, recent, or historical), headline/core figures, labor/employment data, monthly/yearly values, market consensus, whether an event beat or missed expectations, revisions, affected currencies, or release timing. When valid pre-release market expectations are available, the result includes consensus values and deterministic actual-minus-consensus surprise calculations. Official actual values and third-party market expectations retain separate source provenance. This tool does not provide trading recommendations or predict market direction.
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Canonical financial event type. Supported values: US_CPI US_NONFARM_PAYROLLS US_PCE Use these values exactly. |
| referencePeriod | string | – | Optional reference period in YYYY-MM format (e.g. 2026-08). If omitted, the latest available event of that type is returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| affectedCurrencies | array | yes | – |
| category | string | yes | – |
| eventId | string | yes | – |
| eventType | string | yes | – |
| jurisdiction | string | yes | – |
| observations | array | yes | – |
| referencePeriod | string | – | – |
| releasedAt | string | – | – |
| scheduledAt | string | yes | – |
| source | – | yes | – |
| status | string | yes | – |
No examples provided.
get_historical_analogs ~414
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. 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). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Canonical target event type: US_CPI, US_NONFARM_PAYROLLS, or US_PCE. |
| instrument | string | – | Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| maxAnalogs | integer | – | Optional maximum number of individual analogs to return (range 3 to 30, default 10). |
| referencePeriod | string | – | Optional reference period in YYYY-MM format (e.g. 2024-06 or 2026-08). If omitted, the latest available event is resolved as the target. |
| Name | Type | Req | Description |
|---|---|---|---|
| analogs | array | yes | – |
| coverage | object | yes | – |
| eventType | string | yes | – |
| instrument | string | yes | – |
| methodology | object | yes | – |
| methodologyVersion | string | yes | – |
| reactionStatistics | array | yes | – |
| referencePeriod | string | yes | – |
| targetSurprise | – | yes | – |
No examples provided.
get_historical_reaction_context ~400
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. 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). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Canonical target event type: US_CPI or US_NONFARM_PAYROLLS. |
| instrument | string | – | Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| limit | integer | – | Optional maximum number of similar historical events to include in aggregate analysis (range 3 to 30, default 10). |
| referencePeriod | string | – | Optional reference period in YYYY-MM format (e.g. 2024-06 or 2026-08). If omitted, the latest available event is used as the target. |
| Name | Type | Req | Description |
|---|---|---|---|
| aggregatePattern | object | yes | – |
| analogs | array | yes | – |
| coverage | object | yes | – |
| eventType | string | yes | – |
| instrument | string | yes | – |
| reactionStatistics | object | yes | – |
| referencePeriod | string | yes | – |
| targetSurpriseProfile | – | yes | – |
No examples provided.
get_market_reaction ~423
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), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). Optionally specify dateOrPeriod: - For US_CPI, US_PCE, and US_NONFARM_PAYROLLS: 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dateOrPeriod | string | – | Optional reference period (YYYY-MM for US_CPI, US_PCE, and US_NONFARM_PAYROLLS) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned. |
| instrument | string | – | Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| targetType | string | yes | Canonical target event type: US_CPI, US_PCE (alias PCE), US_NONFARM_PAYROLLS (alias NFP), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ). |
| Name | Type | Req | Description |
|---|---|---|---|
| calculatedAt | string | yes | – |
| coverageStatus | string | – | – |
| eventTime | string | yes | – |
| freshness | object | – | – |
| instrument | string | yes | – |
| isComplete | boolean | yes | – |
| isSettled | boolean | yes | – |
| marketDataSource | string | yes | – |
| reactionCoverage | object | – | – |
| reactionId | string | yes | – |
| targetDescription | string | yes | – |
| targetId | string | yes | – |
| targetType | string | yes | – |
| windows | array | yes | – |
No examples provided.
get_upcoming_risks ~250
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, what upcoming macro risks or scheduled events exist, or when the next CPI, next PCE, next Fed, next ECB, next BoE, or next BoJ event occurs. The supported risks are U.S. CPI releases, U.S. PCE inflation releases, Federal Reserve monetary-policy decisions, ECB monetary-policy decisions, Bank of England monetary-policy decisions, and Bank of Japan monetary-policy decisions. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonHours | integer | – | Future time window in hours. Defaults to 24. Maximum is 168 (7 days). |
| instrument | string | – | FX instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | – |
| horizonHours | integer | yes | – |
| instrument | string | yes | – |
| risks | array | yes | – |
| windowEnd | string | yes | – |
No examples provided.
What is the FX Context MCP server?
FX Context is an MCP server listed in the public MCP registry as com.coco-pier/fx-context. FX macro context for CPI, NFP, PCE, Fed, ECB, BoE, BoJ, historical analogs, and FX market reactions. This page covers its hosted endpoint (https://fx.coco-pier.com/mcp).
Is the FX Context MCP server safe to use?
FX Context scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FX Context MCP server expose?
FX Context exposes 6 tools: get_central_bank_changes, get_event_context, get_historical_analogs, get_historical_reaction_context, get_market_reaction, get_upcoming_risks. Their descriptions and schemas cost roughly 1,952 tokens of context every time the server is loaded.
Does the FX Context MCP server require authentication?
No. We connected to FX Context without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FX Context MCP server still maintained?
FX Context is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.