_ registry / mcp streamable-http

fxcontext

https://fx.coco-pier.com

Registry code: 38e57b978f59ef24

api record
endpoint
https://fx.coco-pier.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 6 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_upcoming_risks unknown never probed

    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 Fed, next ECB, next BoE, or next BoJ event occurs. The supported risks are U.S. CPI 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [],
  "properties": {
    "instrument": {
      "type": "string",
      "description": "FX instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD."
    },
    "horizonHours": {
      "type": "integer",
      "format": "int32",
      "description": "Future time window in hours. Defaults to 24. Maximum is 168 (7 days)."
    }
  }
}
    arguments 16 lines
  • get_central_bank_changes unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "centralBank"
  ],
  "properties": {
    "centralBank": {
      "type": "string",
      "description": "Canonical central bank identifier: FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."
    },
    "currentStatementDate": {
      "type": "string",
      "description": "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."
    }
  }
}
    arguments 17 lines
  • get_event_context unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "eventType"
  ],
  "properties": {
    "eventType": {
      "type": "string",
      "description": "Canonical financial event type.\n\nSupported values:\nUS_CPI\nUS_NONFARM_PAYROLLS\nUS_PCE\n\nUse these values exactly."
    },
    "referencePeriod": {
      "type": "string",
      "description": "Optional reference period in YYYY-MM format (e.g. 2026-08). If omitted, the latest available event of that type is returned."
    }
  }
}
    arguments 17 lines
  • get_historical_analogs unknown never probed

    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. 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 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "eventType"
  ],
  "properties": {
    "eventType": {
      "type": "string",
      "description": "Canonical target event type: US_CPI or US_NONFARM_PAYROLLS."
    },
    "instrument": {
      "type": "string",
      "description": "Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD."
    },
    "maxAnalogs": {
      "type": "integer",
      "format": "int32",
      "description": "Optional maximum number of individual analogs to return (range 3 to 30, default 10)."
    },
    "referencePeriod": {
      "type": "string",
      "description": "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."
    }
  }
}
    arguments 26 lines
  • get_historical_reaction_context unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "eventType"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "format": "int32",
      "description": "Optional maximum number of similar historical events to include in aggregate analysis (range 3 to 30, default 10)."
    },
    "eventType": {
      "type": "string",
      "description": "Canonical target event type: US_CPI or US_NONFARM_PAYROLLS."
    },
    "instrument": {
      "type": "string",
      "description": "Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD."
    },
    "referencePeriod": {
      "type": "string",
      "description": "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."
    }
  }
}
    arguments 26 lines
  • get_market_reaction unknown never probed

    Retrieve deterministic post-event market reaction metrics for an economic release or monetary policy statement. Specify the targetType, such as US_CPI, 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 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "targetType"
  ],
  "properties": {
    "instrument": {
      "type": "string",
      "description": "Optional trading instrument: EURUSD, GBPUSD, or USDJPY. Defaults to EURUSD."
    },
    "targetType": {
      "type": "string",
      "description": "Canonical target event type: US_CPI, US_NONFARM_PAYROLLS (alias NFP), FEDERAL_RESERVE, ECB, BANK_OF_ENGLAND (alias BOE), or BANK_OF_JAPAN (alias BOJ)."
    },
    "dateOrPeriod": {
      "type": "string",
      "description": "Optional reference period (YYYY-MM for US_CPI and US_NONFARM_PAYROLLS) or statement date (YYYY-MM-DD for central banks). If omitted, the latest event is returned."
    }
  }
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/38e57b978f59ef24/badge.svg)](https://brick.blue/agent/38e57b978f59ef24)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.