EMpulse Street FX Index
REMOTE · API.EMPULSE.AI
Street FX rates of emerging-market currencies vs USD: latest, history, premium, stress, events
Available components
Last scanned (18 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 0
- Tool “get_hourly” rewrote its description, which is the text the model reads security
- 28 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 121 → 138 ▼ functional
- New tool “get_corridor” functional
- New tool “get_news_sentiment” functional
- New tool “get_rate_stack” functional
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- “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” cosmetic
- 26 Oct 26 68
First indexed and scored.
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 5 Nov 2026 · Probed https://api.empulse.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.empulse.ai | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5336314f891dbf3650348510ddc7862af7f |
| SANs: api.empulse.ai | ||||||
| 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 api.empulse.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| empulse.ai. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.empulse.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.empulse.ai/mcp | HTTPS enforced | 301 | https://api.empulse.ai/mcp |
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_corridor Corridor rate of a currency pair ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | ISO 4217 code, for example EGP, NGN, ARS |
| b | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_fx_events Currency-infrastructure events ~112
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).
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | country name in English |
| currency | – | – | ISO 4217 code |
| days | – | – | 1–90, default 7 |
Structured output declared, but exposes no named fields.
No examples provided.
get_hourly Hourly street rates (Pro) ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | ISO 4217 code, for example EGP, NGN, ARS |
| date | – | – | UTC day, YYYY-MM-DD; default: today |
Structured output declared, but exposes no named fields.
No examples provided.
get_methodology Methodology and how to cite ~40
How the EMpulse Street FX Index is computed — components, confidence classes, outliers, revisions, coverage rules — as markdown, with the citation format.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_news_sentiment News tone of a currency's country ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_official_vs_street Official vs street premium ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_rail_health Payment rails of a country today ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_rail_incidents Payment-rail status changes (Pro) ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | – | ISO 4217 code; omit for all |
| days | – | – | 1–90, default 30 |
Structured output declared, but exposes no named fields.
No examples provided.
get_rate_history Street rate history ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_rate_stack Rate stack of a currency ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_street_rate Street rate of a currency ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_stress_signals FX stress signals ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | – | ISO 4217 code; omit for all |
Structured output declared, but exposes no named fields.
No examples provided.
get_unmet_demand Unmet payment demand ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
Structured output declared, but exposes no named fields.
No examples provided.
get_usdt_liquidity USDT liquidity of a currency ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | 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 |
Structured output declared, but exposes no named fields.
No examples provided.
list_currencies Covered currencies ~58
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
request_free_key Request a free API key ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | the address the key is issued to |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · api.empulse.ai
claude mcp add --transport http empulse-ai-empulse-street-fx 'https://api.empulse.ai/mcp'
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.