Rate-API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RATE_API_KEY | Yes | Your Rate-API key | |
| RATE_API_BASE_URL | No | Override the API base URL | https://rate-api.com |
| RATE_API_TIMEOUT_MS | No | Per-request timeout (ms) | 15000 |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_ratesA | Get the latest exchange rates for a base currency. Returns rates for all currencies (or a filtered subset). |
| convert_currencyA | Convert an amount from one currency to another at the latest rate. Requires Pro plan or higher. |
| get_pair_rateB | Get the exchange rate for a single currency pair, with optional precision. Available on all plans; the converted amount (amount/result) is included on Pro plan or higher. |
| get_historical_ratesA | Get exchange rates for a specific past date (YYYY-MM-DD). Requires Pro plan or higher. |
| get_timeseries_ratesA | Get daily exchange rates for every day between two dates (YYYY-MM-DD, range of at most 366 days), keyed by date. Days without published data are omitted. Pass symbols to keep the response small. Requires Business plan or higher. |
| get_rate_fluctuationA | Get how exchange rates moved between two dates (YYYY-MM-DD, range of at most 366 days): start rate, end rate, absolute change and percent change per currency. Requires Business plan or higher. |
| get_crypto_ratesB | Get cryptocurrency prices in USD (top coins). Requires Pro plan or higher. |
| get_stock_pricesA | Get the latest closing prices for tracked equities, in USD. End-of-day and indicative, not exchange-licensed and not for trading. Requires Pro plan or higher. |
| get_metal_pricesA | Get precious-metal prices per troy ounce in USD: gold (XAU), silver (XAG), platinum (XPT), palladium (XPD). Requires Pro plan or higher. |
| get_key_statusA | Confirm the API key works and report the API status and version. Use get_usage to see the key's plan. |
| list_currenciesA | List all supported currencies (codes and names). |
| get_usageA | Get this API key's plan and current-month usage against its quota (used, limit, remaining, reset date). |
| get_quotaB | Get a lean view of the plan quota and remaining requests for this API key. |
| list_rate_alertsA | List the rate alerts configured on this API key. Requires Business plan or higher. |
| create_rate_alertA | Create a rate alert that fires (by email and optional webhook) when a pair crosses a threshold. Requires Business plan or higher. |
| delete_rate_alertA | Delete a rate alert by its id. Requires Business plan or higher. |
| get_api_statusA | Get Rate-API service status and rate-data freshness (currency count, last update, age). No API key required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| convert_amount | Convert an amount from one currency to another. |
| currency_movement | Summarise how a currency pair has moved recently. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Supported currencies | All supported currency codes with name, symbol and decimal places. |
TDQS
Scored across 17 tools
Several tools have overlapping boundaries: get_usage and get_quota both report quota/usage for the API key, and get_pair_rate/convert_currency can be confused for conversion tasks. While descriptions clarify some differences, the redundancy makes tool selection ambiguous.
All tools use snake_case with a leading verb (get/list/create/delete/convert) and a noun object. The pattern is consistent and predictable across rates, account, and alert operations.
At 17 tools, the server is slightly beyond the ideal 3-15 range, though most tools address a distinct rate or account feature. The count is manageable but borders on heavy for a single-purpose API server.
The server covers latest/historical/timeseries rates, conversion, account usage, and alert lifecycle (create/list/delete), but lacks an update operation for alerts and no dedicated single-alert getter. Minor gaps exist but core workflows are supported.