request_free_key — EMpulse Street FX Index MCP Tool
request_free_key
(request free key) is one of 19 tools on the
EMpulse Street FX Index
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call request_free_key from your client
- Claude Code EMpulse Street FX Index request_free_key run in your project directory
- Claude Desktop EMpulse Street FX Index request_free_key ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EMpulse Street FX Index request_free_key ~/.cursor/mcp.json
- VS Code EMpulse Street FX Index request_free_key .vscode/mcp.json
- Zed EMpulse Street FX Index request_free_key ~/.config/zed/settings.json
- Windsurf EMpulse Street FX Index request_free_key ~/.codeium/windsurf/mcp_config.json
- Cline EMpulse Street FX Index request_free_key ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EMpulse Street FX Index request_free_key ~/.gemini/settings.json
- Grok EMpulse Street FX Index request_free_key .mcp.json (in your project root)
- ChatGPT EMpulse Street FX Index request_free_key Settings → Connectors → Advanced → Developer mode
- Claude.ai EMpulse Street FX Index request_free_key Settings → Connectors → Add custom connector
- LangChain EMpulse Street FX Index request_free_key pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http empulse-street-fx https://api.empulse.ai/mcpOther tools on this server
- 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_news_sentiment
- get_integration_afghanistan
- get_rate_stack
- get_corridor
- get_integration_turkey
- get_street_rates_for_people_b2c
- get_methodology
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.