fxabsolute-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FXA_ORIGIN | No | The base URL of the FXAbsolute website to fetch data from if not available locally. | https://www.fxabsolute.com |
| FXA_DATA_DIR | No | An explicit directory of .bin files containing candle data. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fxa_instrumentsA | List every instrument FXAbsolute has candle data for, with bar counts and pip size. Call this first if you are unsure what is available. Also states plainly which fields exist — notably, this dataset has no volume. |
| fxa_candlesA | Fetch OHLC candles for an instrument over a date range, at any timeframe from M1 to W1. Higher timeframes are aggregated from M1 on true clock boundaries. Returns the most recent bars when the range exceeds the limit. |
| fxa_session_scanA | Pull specific bars out of a trading session across a whole date range, and summarise them. Example: the first 5-minute candle of the New York session every day for six months (instrument SPX500, session nyse, timeframe M5, bars [1]). Session windows are evaluated in exchange-local time with daylight saving handled, so results do not shift by an hour in summer. Use this instead of pulling raw candles and filtering them yourself. |
| fxa_bucket_statsA | Group every bar in a window by hour of day, day of week, month or year, and report how much each bucket moves. Answers "which hour is actually worth trading" and "is Monday different" in one call. Ranked by average bar range, since volume is not available. |
| fxa_level_touchesA | Test whether a price level actually held. Finds every time price reached the level, de-duplicates clustered touches, and measures the reaction that followed. This is the numeric version of asking whether a horizontal line on the chart is respected. |
| fxa_connect_chartA | Pair with a trader's open FXAbsolute chart using the code shown in the AI tab of the backtester. Once connected, the trader can type or speak to you and you answer in their chart panel. Call this when the user gives you a pairing code, e.g. "connect to fxabsolute with code AB3K9P". |
| fxa_wait_for_messageA | Wait for the trader's next message on the paired chart. Blocks until they send something or the timeout expires. Returns their text plus a structured snapshot of the chart at the moment they asked — read that instead of asking them to describe what they are looking at. Returns waiting:false when nothing arrived, in which case call it again to keep listening. |
| fxa_replyA | Send your answer back to the trader's chart panel. Keep it short and concrete — it renders in a narrow side panel next to the chart, not a terminal. |
| fxa_set_thinkingA | Show or hide the thinking indicator in the trader's panel. Call with on:true before a long lookup so they know you are working. fxa_reply clears it automatically. |
| fxa_disconnect_chartA | Leave the paired chart session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/varsansri/fxabsolute-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server