mcpField
E
EMpulse Street FX Index

EMpulse Street FX Index

Remote
empulse.aiFinance0Updated 2d ago

About EMpulse Street FX Index

empulse-mcp is a stdio bridge to the EMpulse Street FX Index for MCP clients that only support stdio. It forwards requests for emerging-market currencies' street rates against the US dollar and related history, stress signals, and event data.

Key features

  1. 01Forward JSON-RPC over stdio
  2. 02Query emerging-market street FX rates
  3. 03Retrieve rate history and official-rate comparisons
  4. 04Query stress signals and FX events
  5. 05Return source, timestamp, and confidence

Use cases

  1. 01Look up a currency's street exchange rate
  2. 02Compare official and street exchange rates
  3. 03Track rate history and market stress signals

MCP support

It forwards requests from stdio MCP clients to the remote MCP server at https://api.empulse.ai/mcp. The remote service provides rate tools and methodology, coverage, and pricing resources.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.empulse.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://api.empulse.ai/mcpAuth required

Tools

Details

From the project README

empulse-mcp

A small stdio bridge to the EMpulse Street FX Index MCP server (https://api.empulse.ai/mcp) for clients that only speak stdio. Standard library only, no build step: every JSON-RPC message from stdin is posted to the remote server and the answer is written to stdout. Clients that support remote servers can skip this package and connect to the URL directly — see https://github.com/empulse-ai/empulse-mcp#connect.

Install and run

uvx empulse-mcp                       # or: pipx run empulse-mcp
EMPULSE_API_KEY=emp_... uvx empulse-mcp

Client configuration (Claude Desktop, Cursor, Windsurf, Zed, …):

{
  "mcpServers": {
    "empulse": {
      "command": "uvx",
      "args": ["empulse-mcp"],
      "env": { "EMPULSE_API_KEY": "emp_..." }
    }
  }
}

Environment: EMPULSE_API_KEY (optional — without it the free level applies: free currencies, data up to yesterday, a daily limit per network), EMPULSE_MCP_URL (default https://api.empulse.ai/mcp).

What the server offers

Street exchange rates of emerging-market currencies against the US dollar — the rate people actually pay where the official rate is managed, lagging or unavailable — built from transaction-based market data and quotes from independent public market sources, with a confidence class and the number of sources on every figure.

Tools: get_street_rate, get_rate_history, list_currencies, get_official_vs_street, get_stress_signals, get_fx_events, get_hourly, get_rail_health, get_rail_incidents, get_unmet_demand, get_usdt_liquidity, get_methodology, request_free_key. Resources: empulse://methodology, empulse://coverage, empulse://pricing. Every answer carries source, as_of, confidence and a ready citation. Full description: https://empulse.ai/llms.txt · API docs: https://api.empulse.ai/docs

Citing

Cite as EMpulse Street FX Index with a link to the currency page (https://empulse.ai/rates/<CUR>). Street rates are not official or interbank rates and not investment advice. Terms: https://empulse.ai/terms

License

MIT for this bridge. The data is served under the EMpulse terms (https://empulse.ai/terms).

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.