# EMpulse Street FX Index (remote · api.empulse.ai)

Street FX rates of emerging-market currencies vs USD: latest, history, premium, stress, events

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.empulse.ai`: 72/100 (this document), [markdown](https://verifymcp.io/servers/empulse-ai-empulse-street-fx/api.md), [page](https://verifymcp.io/servers/empulse-ai-empulse-street-fx/api)

## Channel facts

- Endpoint: `https://api.empulse.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2651 tokens (~139/item across 19 items; 16 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the EMpulse Street FX Index MCP server?

EMpulse Street FX Index is a hosted endpoint at https://api.empulse.ai/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.

### Claude

```bash
claude mcp add --transport http empulse-ai-empulse-street-fx 'https://api.empulse.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "empulse-ai-empulse-street-fx": {
      "url": "https://api.empulse.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "empulse-ai-empulse-street-fx": {
      "type": "http",
      "url": "https://api.empulse.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.empulse-ai-empulse-street-fx]
url = "https://api.empulse.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "empulse-ai-empulse-street-fx": {
      "type": "remote",
      "url": "https://api.empulse.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add empulse-ai-empulse-street-fx --url 'https://api.empulse.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  empulse-ai-empulse-street-fx:
    url: "https://api.empulse.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "empulse-ai-empulse-street-fx": {
      "Transport": "http",
      "Url": "https://api.empulse.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add empulse-ai-empulse-street-fx -t streamable-http -u 'https://api.empulse.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "empulse-ai-empulse-street-fx": {
      "type": "http",
      "url": "https://api.empulse.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 69, 0)

- [security] Tool “get_hourly” rewrote its description, which is the text the model reads

### 2026-10-28 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 121 → 138
- [functional] New tool “get_corridor”
- [functional] New tool “get_news_sentiment”
- [functional] New tool “get_rate_stack”

### 2026-10-27 (score 68, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “get_rail_health” added an optional parameter “lang”
- [cosmetic] “get_unmet_demand” added an optional parameter “lang”
- [cosmetic] “get_usdt_liquidity” added an optional parameter “lang”

### 2026-10-26 (score 68)

First indexed and scored.

## MCP tools (16)

### `get_street_rate` (~166 tokens)

Street rate of a currency

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.

Input parameters:

- `currency` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `date`: UTC day, YYYY-MM-DD; default: the latest day available to your plan
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_rate_history` (~155 tokens)

Street rate history

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.

Input parameters:

- `currency` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `from_date`: first day, YYYY-MM-DD
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English
- `to_date`: last day, YYYY-MM-DD

### `list_currencies` (~58 tokens)

Covered currencies

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_street` (~116 tokens)

Official vs street premium

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.

Input parameters:

- `currency` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_stress_signals` (~100 tokens)

FX stress signals

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.

Input parameters:

- `currency`: ISO 4217 code; omit for all

### `get_fx_events` (~112 tokens)

Currency-infrastructure events

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; `days` back from the latest day of your plan (free: 48-hour delay).

Input parameters:

- `country`: country name in English
- `currency`: ISO 4217 code
- `days`: 1–90, default 7

### `get_hourly` (~107 tokens)

Hourly street rates (Pro)

The street rate of a currency per UTC hour for one day, with the day's summary (vwap, high, low, hours, busiest hour), for every currency with hourly market data; each hour says its component (transaction_based / multi_source / combined) and quality. Pro and Enterprise keys.

Input parameters:

- `currency` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `date`: UTC day, YYYY-MM-DD; default: today

### `get_rail_health` (~179 tokens)

Payment rails of a country today

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.

Input parameters:

- `currency` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_rail_incidents` (~114 tokens)

Payment-rail status changes (Pro)

Every change of status of a payment method class — degraded, outage, back to healthy — over the last `days` (default 30), newest first, each with a one-line summary ("Bank transfers (pay-ins) in Egypt: degraded since 2026-10-24 14:00 UTC"). Optionally one currency. Pro keys of the Rail Health Index.

Input parameters:

- `currency`: ISO 4217 code; omit for all
- `days`: 1–90, default 30

### `get_unmet_demand` (~154 tokens)

Unmet payment demand

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.

Input parameters:

- `currency`: ISO 4217 code; omit for the ranking
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_usdt_liquidity` (~161 tokens)

USDT liquidity of a currency

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.

Input parameters:

- `currency` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_news_sentiment` (~216 tokens)

News tone of a currency's country

What the news says about the country of a currency, day by day. Without a currency: the map of covered currencies ranked by the 7-day fall in the tone of the news. With a currency: its latest day — a label (negative … positive) and the direction of the trend (free level, one day behind); Pro keys of EM FX News & Sentiment also get the score (−1 … 1), the index against the country's own 90-day norm, the number of articles, the early signal when the tone falls while the street rate is calm, the global topics (macro, crypto, markets) and the link between the tone and the next 1-, 3- and 7-day moves of the street rate, with confidence.

Input parameters:

- `currency`: ISO 4217 code; omit for the map
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_rate_stack` (~226 tokens)

Rate stack of a currency

The ladder of rates a currency has on its latest day: the central bank's official rate, the interbank rate, what banks quote (buy / sell), the customs rate duties are computed at, what international cards settle at and the street rate — each with its publication day, the number of sources and a confidence class — the gap of the street over every rung, the width of the ladder, its 7- and 30-day trend and a widening signal (none / watch / alert), with a ready citation. A rung the country does not publish on its own says which rung it equals. Free level: the official, customs and street rungs of the free currencies, one day behind. Paid keys of the FX Rate Stack: every rung, every active currency, today.

Input parameters:

- `currency` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_corridor` (~173 tokens)

Corridor rate of a currency pair

The rate between two emerging-market currencies as quoted in public exchange listings between the two countries (units of `b` per 1 `a`), the day's range, the number of sources and the confidence class, next to the cross rate implied by the two dollar legs of the index and the corridor premium (positive: going directly is dearer than through the dollar). Pro and Enterprise keys of the index.

Input parameters:

- `a` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `b` (string, required): ISO 4217 code, for example EGP, NGN, ARS
- `lang`: Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English

### `get_methodology` (~40 tokens)

Methodology and how to cite

How the EMpulse Street FX Index is computed — components, confidence classes, outliers, revisions, coverage rules — as markdown, with the citation format.

### `request_free_key` (~83 tokens)

Request a free API key

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.

Input parameters:

- `email` (string, required): the address the key is issued to

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/empulse-ai-empulse-street-fx/api#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68

## Common questions

### What is the EMpulse Street FX Index MCP server?

EMpulse Street FX Index is an MCP server listed in the public MCP registry as io.github.empulse-ai/empulse-street-fx. Street FX rates of emerging-market currencies vs USD: latest, history, premium, stress, events. This page covers its hosted endpoint (https://api.empulse.ai/mcp).

### Is the EMpulse Street FX Index MCP server safe to use?

EMpulse Street FX Index scores 72 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 EMpulse Street FX Index MCP server expose?

EMpulse Street FX Index exposes 16 tools: get_street_rate, get_rate_history, list_currencies, get_official_vs_street, get_stress_signals, and 11 more. Their descriptions and schemas cost roughly 2,160 tokens of context every time the server is loaded.

### Does the EMpulse Street FX Index MCP server require authentication?

No. We connected to EMpulse Street FX Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the EMpulse Street FX Index MCP server still maintained?

EMpulse Street FX Index is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the EMpulse Street FX Index MCP server?

VerifyMCP ran 12 checks on EMpulse Street FX Index, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about EMpulse Street FX Index: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.empulse.ai/mcp
- Repository: https://github.com/empulse-ai/empulse-mcp
- Website: https://empulse.ai/
- Changelog RSS feed: https://verifymcp.io/servers/empulse-ai-empulse-street-fx/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/empulse-ai-empulse-street-fx/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/empulse-ai-empulse-street-fx/api.json
- HTML version of this page: https://verifymcp.io/servers/empulse-ai-empulse-street-fx/api