EMpulse Street FX Index
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMPULSE_API_KEY | No | Optional API key. Without it the free level applies: free currencies, data up to yesterday, a daily limit per network. | |
| EMPULSE_MCP_URL | No | The URL of the remote EMpulse MCP server. | https://api.empulse.ai/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_street_rateA | The latest street exchange rate of an emerging-market currency against the US dollar (USDT) from the EMpulse Street FX Index, or the rate on a given day: rate (mid), buy, sell, spread, 1/7/30-day changes, confidence class and a ready citation. Free access is delayed by one day; a Pro key gives the current day. |
| get_rate_historyA | Daily street rates of a currency between two dates (inclusive, UTC days, at most 400 days per call): rate, buy, sell, confidence per day, plus a summary (first, last, change, low, high). Defaults: the last 30 days up to the latest day of your plan. |
| list_currenciesA | Every currency of the EMpulse Street FX Index with its status (active, or coverage in progress while market sources are being added), the confidence class and the number of sources behind the latest day, coverage since, and whether your plan covers it. |
| get_official_vs_streetB | How far the street rate of a currency is from its official central-bank rate: official rate and its publication day, street rate, premium in percent, 7-day average and 30-day maximum. Pro and Enterprise keys. |
| get_stress_signalsA | Early warning from the street: a none / watch / alert flag per currency when the street market shows stress (a run of weakening days, a 7-day move in the top decile of the currency's own year, a buy–sell spread blow-out), with the rules that fired and the day the episode started. One currency or all. Pro and Enterprise keys. |
| get_fx_eventsA | A dated feed of events that move street FX in emerging markets — devaluations, cash and withdrawal limits, bans of stablecoin services, currency controls, payment outages — each a short quotation with a link to the public source. Filter by country or currency; |
| get_hourlyA | The street rate of a currency per UTC hour for one day, with the day's summary (vwap, high, low, hours, busiest hour). Pro and Enterprise keys; hours arrive with the daily update. |
| get_rail_healthA | Which payment methods work in a country today and how reliably: for every method class (cards, bank transfers, instant transfers, e-wallets, mobile money, cash, crypto, direct local rails) and direction (pay-ins, payouts) a status — healthy / degraded / outage / no_data — with the time it began and a ready citation. Free level: the free currencies, one day behind. Pro keys of the Rail Health Index: today, every currency, the health index (100 = the rail's own norm), availability, supply. |
| get_rail_incidentsA | Every change of status of a payment method class — degraded, outage, back to healthy — over the last |
| get_unmet_demandA | Where payment demand in emerging markets is not being served. Without a currency: the ranking of covered markets by the share of demand no rail served, with the trend. With a currency: its rank and trend (free level, one day behind); Pro keys of the Unmet Demand Map also get the unmet share, the not-connected share, the index against the 90-day norm, the reason classes and the hours of day, per direction and method class. |
| get_usdt_liquidityA | Where and when the dollar actually moves through USDT: the liquidity index of a currency (0–100, 50 = the market's own 90-day norm) with a ready citation. Free level: yesterday, the free currencies. Pro keys of USDT Liquidity & Premium: today, every currency, the pay-in / payout balance, the spread, the active hours of day, the premium over the official rate and the supply class. |
| get_methodologyA | How the EMpulse Street FX Index is computed — components, confidence classes, outliers, revisions, coverage rules — as markdown, with the citation format. |
| request_free_keyA | Issue a free EMpulse API key for an email address, right here: the free currencies, data up to yesterday, 100 calls per day. The key is returned and also emailed with a ready example; send it in the X-API-Key header on this server and on the REST API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| methodology | How the EMpulse Street FX Index is computed and how to cite it (markdown). |
| coverage | Every currency of the index with status, confidence and sources (public view, one-day delay). |
| pricing | Free, Pro and Enterprise plans of the index. |
TDQS
Scored across 13 tools
Each tool targets a clearly distinct data product or time granularity: latest rate, historical range, hourly rates, official-vs-street premium, stress signals, events, rail health, rail incidents, unmet demand, and USDT liquidity. The descriptions make the boundaries explicit, so an agent should not confuse similar-sounding tools like get_street_rate, get_rate_history, and get_hourly.
All tools use snake_case with a predictable verb_noun or verb_noun_phrase pattern: get_*, list_*, and request_*. There are no mixed conventions or vague names.
The set has 13 tools, which is well within a reasonable range for a multi-index FX and payments data API. Each tool appears to correspond to a distinct dataset or operation, with no obvious filler.
The surface covers the core lifecycle for this data domain: latest rates, history, hourly data, currency coverage, official comparisons, stress signals, events, rail health and incidents, unmet demand, USDT liquidity, methodology, and free-key issuance. Minor gaps remain, such as no explicit multi-currency latest-rate batch operation or account/usage management beyond requesting a free key, but agents can work around these.