Rate-API MCP Server
Related Servers
Alternatives to Rate-API MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceReal-time currency exchange rates and crypto prices via MCP. Convert between 60+ fiat currencies and 30+ cryptocurrencies with multi-source failover. No API keys needed for upstream data.6 npmISC
- AlicenseAqualityBmaintenanceProvides real-time foreign-exchange rates, historical data, and multi-currency lookups to MCP-compatible AI coding assistants like Claude Code and Cursor.4130 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to fetch official published exchange rates from 60+ central banks and tax authorities, with point-in-time lookup, history, and cross-bank comparison.564 npm1MIT
- AlicenseNot gradedqualityAmaintenanceConvert currencies, get FX rates, and query historical ECB exchange rate data via MCP.442 npm1Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceMCP server that provides real exchange-rate data from the European Central Bank, including latest rates, currency conversion, historical rates, and time series.-
- FlicenseBqualityDmaintenanceAn MCP server that provides currency rates, conversions, and historical exchange-rate data using the Frankfurter API. It enables users to retrieve latest rates, convert amounts between currencies, and access time-series data for currency pairs.3-
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.