FrankfurterMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SSL_CERT_DIR | No | SSL certificate directory path for self-signed certificates of hosted API endpoint or intermediate HTTP(S) proxy server(s). | |
| FAST_MCP_HOST | No | This variable specifies which host the MCP server must bind to unless the server transport (see below) is set to stdio. | 0.0.0.0 |
| FAST_MCP_PORT | No | This variable specifies which port the MCP server must listen on unless the server transport (see below) is set to stdio. | 8000 |
| HTTPX_TIMEOUT | No | The time for the underlying HTTP client to wait, in seconds, for a response from the Frankfurter API. | 5.0 |
| SSL_CERT_FILE | No | SSL certificate file path for self-signed certificates of hosted API endpoint or intermediate HTTP(S) proxy server(s). | |
| HTTPX_VERIFY_SSL | No | This variable can be set to False to turn off SSL certificate verification, if, for instance, you are using a proxy server with a self-signed certificate. However, setting this to False is advised against: instead, use the SSL_CERT_FILE and SSL_CERT_DIR variables to properly configure self-signed certificates. | True |
| FRANKFURTER_API_URL | No | If you are self-hosting the Frankfurter API, you should change this to the API endpoint address of your deployment. | https://api.frankfurter.dev/v1 |
| MCP_SERVER_TRANSPORT | No | The acceptable options are stdio, sse or streamable-http. However, in the .env.template, the default value is set to streamable-http. | stdio |
| MCP_SERVER_INCLUDE_METADATA_IN_RESPONSE | No | An experimental feature to include additional metadata to the MCP type TextContent that wraps the response data from each tool call. The additional metadata, for example, will include (as of June 21, 2025) the API URL of the Frankfurter server that is used to obtain the responses. | True |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_supported_currenciesA | Returns a list of three-letter currency codes for the supported currencies. |
| get_latest_exchange_ratesB | Returns the latest exchange rates for specific currencies. The symbols can be used to filter the results to specific currencies. If symbols is not provided, all supported currencies will be returned. |
| convert_currency_latestA | Converts an amount from one currency to another using the latest exchange rates. |
| get_historical_exchange_ratesA | Returns historical exchange rates for a specific date or date range. If the exchange rates for a specified date is not available, the rates available for the closest date before the specified date will be provided. Either a specific date, a start date, or a date range must be provided. The symbols can be used to filter the results to specific currencies. If symbols are not provided, all supported currencies will be returned. |
| convert_currency_specific_dateA | Convert an amount from one currency to another using the exchange rates for a specific date. If there is no exchange rate available for the specific date, the rate for the closest available date before the specified date will be used. |
| greetD | A simple greeting tool to demonstrate middleware functionality. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The currency tools are clearly separated by action (fetch/convert) and time (latest/historical), and each has a distinct purpose. The 'greet' tool is completely unrelated but its intent is obvious, so it doesn't cause confusion with the currency operations; however, it introduces a minor scope ambiguity.
Most tools use a get_/convert_ prefix, but structure is mixed: 'convert_currency_latest' and 'convert_currency_specific_date' place the time qualifier awkwardly at the end, unlike 'get_latest_exchange_rates' which uses 'latest' as an adjective before the noun. The 'greet' tool breaks the pattern entirely.
Six tools is a reasonable size for a currency exchange server, and the core set is well-scoped. The inclusion of 'greet' as a middleware demo is an unnecessary addition that dilutes the tool surface, making it slightly less focused than it should be.
The server covers supported currencies, latest rates, historical rates, and conversions for both latest and specific dates—essentially all core exchange-rate operations. There are no significant dead ends or missing features that would prevent an agent from completing common currency-related tasks.