[](https://www.python.org/downloads/release/python-3120/) [](https://github.com/anirbanbasu/frankfurtermcp/actions/workflows/uv-pytest.yml) 
[](https://pypi.org/project/frankfurtermcp/#history)
[](https://pypi.org/project/frankfurtermcp/)
[](https://mseep.ai/app/c6527bdb-9b60-430d-9ed6-cb3c8b9a2b54) [](https://smithery.ai/server/@anirbanbasu/frankfurtermcp)
# Frankfurter MCP
[Frankfurter](https://frankfurter.dev/) is a useful API for latest currency exchange rates, historical data, or time series published by sources such as the European Central Bank. Should you have to access the Frankfurter API as tools for language model agents exposed over the Model Context Protocol (MCP), Frankfurter MCP is what you need.
# Installation
_If your objective is to use the tools available on this MCP server, please refer to the usage > client sub-section below_.
The directory where you clone this repository will be referred to as the _working directory_ or _WD_ hereinafter.
Install [uv](https://docs.astral.sh/uv/getting-started/installation/). To install the project with its minimal dependencies in a virtual environment, run the following in the _WD_. To install all non-essential dependencies (_which are required for developing and testing_), replace the `--no-dev` with the `--all-groups` flag in the following command.
```bash
uv sync --no-dev
```
## Environment variables
Following is a list of environment variables that can be used to configure the application. A template of environment variables is provided in the file `.env.template`.
The following environment variables can be specified, prefixed with `FASTMCP_`: `HOST`, `PORT`, `DEBUG` and `LOG_LEVEL`. See [global configuration options](https://gofastmcp.com/servers/server#global-settings) for FastMCP. Note that `on_duplicate_` prefixed options specified as environment variables _will be ignored_.
The underlying HTTP client also respects some environment variables, as documented in [the HTTPX library](https://www.python-httpx.org/environment_variables/). In addition, `SSL_CERT_FILE` and `SSL_CERT_DIR` can be configured to use self-signed certificates of hosted API endpoint or intermediate HTTP(S) proxy server(s).
| Variable | [Default value] and description |
|--------------|----------------|
| `HTTPX_TIMEOUT` | [5.0] The time for the underlying HTTP client to wait, in seconds, for a response from the Frankfurter API. |
| `HTTPX_VERIFY_SSL` | [True] 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. |
| `FAST_MCP_HOST` | [0.0.0.0] This variable specifies which host the MCP server must bind to unless the server transport (see below) is set to `stdio`. |
| `FAST_MCP_PORT` | [8000] This variable specifies which port the MCP server must listen on unless the server transport (see below) is set to `stdio`. |
| `MCP_SERVER_TRANSPORT` | [stdio] The acceptable options are `stdio`, `sse` or `streamable-http`. However, in the `.env.template`, the default value is set to `streamable-http`. |
| `MCP_SERVER_INCLUDE_METADATA_IN_RESPONSE` | [True] 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. |
| `FRANKFURTER_API_URL` | [https://api.frankfurter.dev/v1] If you are [self-hosting the Frankfurter API](https://hub.docker.com/r/lineofflight/frankfurter), you should change this to the API endpoint address of your deployment. |
# Usage
The following sub-sections illustrate how to run the Frankfurter MCP as a server and how to access it from MCP clients.
## Server
While running the server, you have the choice to use `stdio` transport or HTTP options (`sse` or the newer `streamable-http`).
Using default settings and `MCP_SERVER_TRANSPORT` set to `sse` or `streamable-http`, the MCP endpoint will be available over HTTP at [http://localhost:8000/sse](http://localhost:8000/sse) for the Server Sent Events (SSE) transport, or [http://localhost:8000/mcp](http://localhost:8000/mcp) for the streamable HTTP transport.
If you want to run Frankfurter MCP with `stdio` transport and the default parameters, execute the commands below without using the `.env.template` file.
### Server with `uv`
_Optional_: Copy the `.env.template` file to a `.env` file in the _WD_, to modify the aforementioned environment variables, if you want to use anything other than the default settings. Or, on your shell, you can export the environment variables that you wish to modify.
Run the following in the _WD_ to start the MCP server.
```bash
uv run frankfurtermcp
```
### Server with `pip` from PyPI package
Add this package from PyPI using `pip` in a virtual environment (possibly managed by `conda` or `pyenv`) and then start the server by running the following.
_Optional_: Add a `.env` file with the contents of the `.env.template` file if you wish to modify the default values of the aforementioned environment variables. Or, on your shell, you can export the environment variables that you wish to modify.
```bash
pip install frankfurtermcp
python -m frankfurtermcp.server
```
### Server using Docker
There are two Dockerfiles provided in this repository.
- `local.dockerfile` for containerising the Frankfurter MCP server.
- `smithery.dockerfile` for deploying to [Smithery AI](https://smithery.ai/), which you do not have to use.
To build the image, create the container and start it, run the following in _WD_. _Choose shorter names for the image and container if you prefer._
If you change the port to anything other than 8000 in `.env.template`, _do remember to change the port number references in the following command_. Instead of passing all the environment variables using the `--env-file` option, you can also pass individual environment variables using the `-e` option.
```bash
docker build -t frankfurtermcp -f local.dockerfile .
docker create -p 8000:8000/tcp --env-file .env.template --expose 8000 --name frankfurtermcp-container frankfurtermcp
docker start frankfurtermcp-container
```
Upon successful build and container start, the MCP server will be available over HTTP at [http://localhost:8000/sse](http://localhost:8000/sse) for the Server Sent Events (SSE) transport, or [http://localhost:8000/mcp](http://localhost:8000/mcp) for the streamable HTTP transport.
### Dynamic mounting with FastMCP
To see how to use the MCP server by mounting it dynamically with [FastMCP](https://gofastmcp.com/) as part of your own MCP server, check the file [`src/frankfurtermcp/composition.py`](https://github.com/anirbanbasu/frankfurtermcp/blob/master/src/frankfurtermcp/composition.py).
### Cloud hosted servers
The currently available cloud hosted options are as follows.
- Glama.AI: https://glama.ai/mcp/servers/@anirbanbasu/frankfurtermcp
- Smithery.AI: https://smithery.ai/server/@anirbanbasu/frankfurtermcp
## Client access
This sub-section explains ways for a client to connect and test the FrankfurterMCP server. A command-line interface (CLI) is also provided for testing, which is explained in a later sub-section.
### The official MCP visual inspector
The [MCP Inspector](https://github.com/modelcontextprotocol/inspector) is an _official_ Model Context Protocol tool that can be used by developers to test and debug MCP servers. This is the most comprehensive way to explore the MCP server.
To use it, you must have Node.js installed. The best way to install and manage `node` as well as packages such as the MCP Inspector is to use the [Node Version Manager (or, `nvm`)](https://github.com/nvm-sh/nvm). Once you have `nvm` installed, you can install and use the latest Long Term Release version of `node` by executing the following.
```bash
nvm install --lts
nvm use --lts
```
Following that (install and) run the MCP Inspector by executing the following in the _WD_.
```bash
npx @modelcontextprotocol/inspector uv run frankfurtermcp
```
This will create a local URL at port 6274 with an authentication token, which you can copy and browse to on your browser. Once on the MCP Inspector UI, press _Connect_ to connect to the MCP server. Thereafter, you can explore the tools available on the server.
### Claude Desktop, Visual Studio, and so on
The server entry to run with `stdio` transport that you can use with systems such as Claude Desktop, Visual Studio Code, and so on is as follows.
```json
{
"command": "uv",
"args": [
"run",
"frankfurtermcp"
]
}
```
Instead of having `frankfurtermcp` as the last item in the list of `args`, you may need to specify the full path to the script, e.g., _WD_`/.venv/bin/frankfurtermcp`. Likewise, instead of using `uv`, you could also have the following JSON configuration with the path properly substituted for `python3.12`, for instance such as _WD_`/.venv/bin/python3.12`.
```json
{
"command": "python3.12",
"args": [
"-m",
"frankfurtermcp.server"
]
}
```
# List of available tools
The following table lists the names of the tools as exposed by the FrankfurterMCP server. It does not list the tool(s) exposed through [the composition example](https://github.com/anirbanbasu/frankfurtermcp/blob/master/src/frankfurtermcp/composition.py). The descriptions shown here are for documentation purposes, which may differ from the actual descriptions exposed over the model context protocol.
| Name | Description |
|--------------|----------------|
| `get_supported_currencies` | Get a list of currencies supported by the Frankfurter API. |
| `get_latest_exchange_rates` | Get latest exchange rates in specific currencies for a given base currency. |
| `convert_currency_latest` | Convert an amount from one currency to another using the latest exchange rates. |
| `get_historical_exchange_rates` | Get historical exchange rates for a specific date or date range in specific currencies for a given base currency. |
| `convert_currency_specific_date` | Convert an amount from one currency to another using the exchange rates for a specific date. |
The required and optional arguments for each tool are not listed in the following table for brevity but are available to the MCP client over the protocol.
## FrankfurterMCP command-line interface (CLI)
You may also use the CLI provided with FrankfurterMCP to explore the tools of the MCP server. For example, to see the detailed schema for a particular tool, you can do so using the `tools-info` commmand from the command line interface. The command line interface is available as the script `cli`. You can invoke its help to see the available commands as follows.
```bash
uv run cli --help
```
This will produce an output similar to the screenshot below.
Before calling the `tools-info` command, you **MUST** have the server running in `streamable-http` or `sse` transport mode, preferably locally, e.g., by invoking `MCP_SERVER_TRANSPORT=streamable-http uv run frankfurtermcp`. A successful call of the `tools-info` command will generate an output similar to the screenshot shown below.
Alternative to the `tools-info` command, you can also run call the `llamaindex-tools-list` command to display the names of the tools without the respective function schemas. This functionality is provided only to optionally demonstrate that the LlamaIndex MCP client can read the tools list from this MCP server. In order for this to function, you must install LlamaIndex MCP client by calling `uv sync --extra opt`. The output of calling this command will look like the following.
# Contributing
Install [`pre-commit`](https://pre-commit.com/) for Git and [`ruff`](https://docs.astral.sh/ruff/installation/). Then enable `pre-commit` by running the following in the _WD_.
```bash
pre-commit install
```
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
# Testing
To run the provided test cases, execute the following. Add the flag `--capture=tee-sys` to the command to display further console output.
_Note that for the tests to succeed, the environment variable `MCP_SERVER_TRANSPORT` must be set to either `sse` or `streamable-http`. If not set, it will default to `stdio` and the tests will fail_.
```bash
MCP_SERVER_TRANSPORT=streamable-http uv run --group test pytest tests/
```
# License
[MIT](https://choosealicense.com/licenses/mit/).
# Project status
Following is a table of some updates regarding the project status. Note that these do not correspond to specific commits or milestones.
| Date | Status | Notes or observations |
|----------|:-------------:|----------------------|
| June 27, 2025 | active | Successful remote deployments on Glama.AI and Smithery.AI. |
| June 13, 2025 | active | Added LlamaIndex tool listing for demonstration only. (The `--all-extras` flag is necessary to install LlamaIndex, which is not installed by default.) |
| June 9, 2025 | active | Added containerisation, support for self-signed, proxies. |
| June 8, 2025 | active | Added dynamic composition. |
| June 7, 2025 | active | Added tools to cover all the functionalities of the Frankfurter API. |
| June 7, 2025 | active | Project started. |
Raw data
{
"_id": null,
"home_page": null,
"name": "frankfurtermcp",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.12",
"maintainer_email": null,
"keywords": "currency-converter, currency-exchange-rates, fastmcp, finance, frankfurter-api, mcp, mcp-composition, mcp-server, model-context-protocol, model-context-protocol-server",
"author": null,
"author_email": "Anirban Basu <anirbanbasu@users.noreply.github.com>",
"download_url": "https://files.pythonhosted.org/packages/fa/d3/76fb1e3496a2422d2a2b4f0db8bcf8236ac9281005a2322dfa44e2c70935/frankfurtermcp-0.3.3.tar.gz",
"platform": null,
"description": "[](https://www.python.org/downloads/release/python-3120/) [](https://github.com/anirbanbasu/frankfurtermcp/actions/workflows/uv-pytest.yml) \n [](https://pypi.org/project/frankfurtermcp/#history)\n[](https://pypi.org/project/frankfurtermcp/)\n[](https://mseep.ai/app/c6527bdb-9b60-430d-9ed6-cb3c8b9a2b54) [](https://smithery.ai/server/@anirbanbasu/frankfurtermcp)\n\n# Frankfurter MCP\n\n[Frankfurter](https://frankfurter.dev/) is a useful API for latest currency exchange rates, historical data, or time series published by sources such as the European Central Bank. Should you have to access the Frankfurter API as tools for language model agents exposed over the Model Context Protocol (MCP), Frankfurter MCP is what you need.\n\n# Installation\n\n_If your objective is to use the tools available on this MCP server, please refer to the usage > client sub-section below_.\n\nThe directory where you clone this repository will be referred to as the _working directory_ or _WD_ hereinafter.\n\nInstall [uv](https://docs.astral.sh/uv/getting-started/installation/). To install the project with its minimal dependencies in a virtual environment, run the following in the _WD_. To install all non-essential dependencies (_which are required for developing and testing_), replace the `--no-dev` with the `--all-groups` flag in the following command.\n\n```bash\nuv sync --no-dev\n```\n\n## Environment variables\n\nFollowing is a list of environment variables that can be used to configure the application. A template of environment variables is provided in the file `.env.template`.\n\nThe following environment variables can be specified, prefixed with `FASTMCP_`: `HOST`, `PORT`, `DEBUG` and `LOG_LEVEL`. See [global configuration options](https://gofastmcp.com/servers/server#global-settings) for FastMCP. Note that `on_duplicate_` prefixed options specified as environment variables _will be ignored_.\n\nThe underlying HTTP client also respects some environment variables, as documented in [the HTTPX library](https://www.python-httpx.org/environment_variables/). In addition, `SSL_CERT_FILE` and `SSL_CERT_DIR` can be configured to use self-signed certificates of hosted API endpoint or intermediate HTTP(S) proxy server(s).\n\n| Variable | [Default value] and description |\n|--------------|----------------|\n| `HTTPX_TIMEOUT` | [5.0] The time for the underlying HTTP client to wait, in seconds, for a response from the Frankfurter API. |\n| `HTTPX_VERIFY_SSL` | [True] 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. |\n| `FAST_MCP_HOST` | [0.0.0.0] This variable specifies which host the MCP server must bind to unless the server transport (see below) is set to `stdio`. |\n| `FAST_MCP_PORT` | [8000] This variable specifies which port the MCP server must listen on unless the server transport (see below) is set to `stdio`. |\n| `MCP_SERVER_TRANSPORT` | [stdio] The acceptable options are `stdio`, `sse` or `streamable-http`. However, in the `.env.template`, the default value is set to `streamable-http`. |\n| `MCP_SERVER_INCLUDE_METADATA_IN_RESPONSE` | [True] 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. |\n| `FRANKFURTER_API_URL` | [https://api.frankfurter.dev/v1] If you are [self-hosting the Frankfurter API](https://hub.docker.com/r/lineofflight/frankfurter), you should change this to the API endpoint address of your deployment. |\n\n# Usage\n\nThe following sub-sections illustrate how to run the Frankfurter MCP as a server and how to access it from MCP clients.\n\n## Server\nWhile running the server, you have the choice to use `stdio` transport or HTTP options (`sse` or the newer `streamable-http`).\n\nUsing default settings and `MCP_SERVER_TRANSPORT` set to `sse` or `streamable-http`, the MCP endpoint will be available over HTTP at [http://localhost:8000/sse](http://localhost:8000/sse) for the Server Sent Events (SSE) transport, or [http://localhost:8000/mcp](http://localhost:8000/mcp) for the streamable HTTP transport.\n\nIf you want to run Frankfurter MCP with `stdio` transport and the default parameters, execute the commands below without using the `.env.template` file.\n\n### Server with `uv`\n\n_Optional_: Copy the `.env.template` file to a `.env` file in the _WD_, to modify the aforementioned environment variables, if you want to use anything other than the default settings. Or, on your shell, you can export the environment variables that you wish to modify.\n\nRun the following in the _WD_ to start the MCP server.\n\n```bash\nuv run frankfurtermcp\n```\n\n### Server with `pip` from PyPI package\n\nAdd this package from PyPI using `pip` in a virtual environment (possibly managed by `conda` or `pyenv`) and then start the server by running the following.\n\n_Optional_: Add a `.env` file with the contents of the `.env.template` file if you wish to modify the default values of the aforementioned environment variables. Or, on your shell, you can export the environment variables that you wish to modify.\n\n```bash\npip install frankfurtermcp\npython -m frankfurtermcp.server\n```\n\n### Server using Docker\n\nThere are two Dockerfiles provided in this repository.\n\n - `local.dockerfile` for containerising the Frankfurter MCP server.\n - `smithery.dockerfile` for deploying to [Smithery AI](https://smithery.ai/), which you do not have to use.\n\nTo build the image, create the container and start it, run the following in _WD_. _Choose shorter names for the image and container if you prefer._\n\nIf you change the port to anything other than 8000 in `.env.template`, _do remember to change the port number references in the following command_. Instead of passing all the environment variables using the `--env-file` option, you can also pass individual environment variables using the `-e` option.\n\n```bash\ndocker build -t frankfurtermcp -f local.dockerfile .\ndocker create -p 8000:8000/tcp --env-file .env.template --expose 8000 --name frankfurtermcp-container frankfurtermcp\ndocker start frankfurtermcp-container\n```\n\nUpon successful build and container start, the MCP server will be available over HTTP at [http://localhost:8000/sse](http://localhost:8000/sse) for the Server Sent Events (SSE) transport, or [http://localhost:8000/mcp](http://localhost:8000/mcp) for the streamable HTTP transport.\n\n### Dynamic mounting with FastMCP\n\nTo see how to use the MCP server by mounting it dynamically with [FastMCP](https://gofastmcp.com/) as part of your own MCP server, check the file [`src/frankfurtermcp/composition.py`](https://github.com/anirbanbasu/frankfurtermcp/blob/master/src/frankfurtermcp/composition.py).\n\n### Cloud hosted servers\n\nThe currently available cloud hosted options are as follows.\n\n - Glama.AI: https://glama.ai/mcp/servers/@anirbanbasu/frankfurtermcp\n - Smithery.AI: https://smithery.ai/server/@anirbanbasu/frankfurtermcp\n\n\n## Client access\n\nThis sub-section explains ways for a client to connect and test the FrankfurterMCP server. A command-line interface (CLI) is also provided for testing, which is explained in a later sub-section.\n\n### The official MCP visual inspector\n\nThe [MCP Inspector](https://github.com/modelcontextprotocol/inspector) is an _official_ Model Context Protocol tool that can be used by developers to test and debug MCP servers. This is the most comprehensive way to explore the MCP server.\n\nTo use it, you must have Node.js installed. The best way to install and manage `node` as well as packages such as the MCP Inspector is to use the [Node Version Manager (or, `nvm`)](https://github.com/nvm-sh/nvm). Once you have `nvm` installed, you can install and use the latest Long Term Release version of `node` by executing the following.\n\n```bash\nnvm install --lts\nnvm use --lts\n```\n\nFollowing that (install and) run the MCP Inspector by executing the following in the _WD_.\n\n```bash\nnpx @modelcontextprotocol/inspector uv run frankfurtermcp\n```\n\nThis will create a local URL at port 6274 with an authentication token, which you can copy and browse to on your browser. Once on the MCP Inspector UI, press _Connect_ to connect to the MCP server. Thereafter, you can explore the tools available on the server.\n\n### Claude Desktop, Visual Studio, and so on\n\nThe server entry to run with `stdio` transport that you can use with systems such as Claude Desktop, Visual Studio Code, and so on is as follows.\n\n```json\n{\n \"command\": \"uv\",\n \"args\": [\n \"run\",\n \"frankfurtermcp\"\n ]\n}\n```\n\nInstead of having `frankfurtermcp` as the last item in the list of `args`, you may need to specify the full path to the script, e.g., _WD_`/.venv/bin/frankfurtermcp`. Likewise, instead of using `uv`, you could also have the following JSON configuration with the path properly substituted for `python3.12`, for instance such as _WD_`/.venv/bin/python3.12`.\n\n```json\n{\n \"command\": \"python3.12\",\n \"args\": [\n \"-m\",\n \"frankfurtermcp.server\"\n ]\n}\n```\n\n# List of available tools\n\nThe following table lists the names of the tools as exposed by the FrankfurterMCP server. It does not list the tool(s) exposed through [the composition example](https://github.com/anirbanbasu/frankfurtermcp/blob/master/src/frankfurtermcp/composition.py). The descriptions shown here are for documentation purposes, which may differ from the actual descriptions exposed over the model context protocol.\n\n| Name | Description |\n|--------------|----------------|\n| `get_supported_currencies` | Get a list of currencies supported by the Frankfurter API. |\n| `get_latest_exchange_rates` | Get latest exchange rates in specific currencies for a given base currency. |\n| `convert_currency_latest` | Convert an amount from one currency to another using the latest exchange rates. |\n| `get_historical_exchange_rates` | Get historical exchange rates for a specific date or date range in specific currencies for a given base currency. |\n| `convert_currency_specific_date` | Convert an amount from one currency to another using the exchange rates for a specific date. |\n\nThe required and optional arguments for each tool are not listed in the following table for brevity but are available to the MCP client over the protocol.\n\n## FrankfurterMCP command-line interface (CLI)\nYou may also use the CLI provided with FrankfurterMCP to explore the tools of the MCP server. For example, to see the detailed schema for a particular tool, you can do so using the `tools-info` commmand from the command line interface. The command line interface is available as the script `cli`. You can invoke its help to see the available commands as follows.\n\n```bash\nuv run cli --help\n```\n\nThis will produce an output similar to the screenshot below.\n\n![cli-help-screenshot](https://raw.githubusercontent.com/anirbanbasu/frankfurtermcp/master/screenshots/cli-help.png \"FrankfurterMCP CLI help\")\n\nBefore calling the `tools-info` command, you **MUST** have the server running in `streamable-http` or `sse` transport mode, preferably locally, e.g., by invoking `MCP_SERVER_TRANSPORT=streamable-http uv run frankfurtermcp`. A successful call of the `tools-info` command will generate an output similar to the screenshot shown below.\n\n![cli-tools-info-screenshot](https://raw.githubusercontent.com/anirbanbasu/frankfurtermcp/master/screenshots/cli-tools-info.png \"FrankfurterMCP CLI tools-info\")\n\nAlternative to the `tools-info` command, you can also run call the `llamaindex-tools-list` command to display the names of the tools without the respective function schemas. This functionality is provided only to optionally demonstrate that the LlamaIndex MCP client can read the tools list from this MCP server. In order for this to function, you must install LlamaIndex MCP client by calling `uv sync --extra opt`. The output of calling this command will look like the following.\n\n![cli-llamaindex-tools-list-screenshot](https://raw.githubusercontent.com/anirbanbasu/frankfurtermcp/master/screenshots/cli-llamaindex-tools-list.png \"FrankfurterMCP CLI llamaindex-tools-list\")\n\n# Contributing\n\nInstall [`pre-commit`](https://pre-commit.com/) for Git and [`ruff`](https://docs.astral.sh/ruff/installation/). Then enable `pre-commit` by running the following in the _WD_.\n\n```bash\npre-commit install\n```\nPull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.\n\n# Testing\n\nTo run the provided test cases, execute the following. Add the flag `--capture=tee-sys` to the command to display further console output.\n\n_Note that for the tests to succeed, the environment variable `MCP_SERVER_TRANSPORT` must be set to either `sse` or `streamable-http`. If not set, it will default to `stdio` and the tests will fail_.\n\n```bash\nMCP_SERVER_TRANSPORT=streamable-http uv run --group test pytest tests/\n```\n\n# License\n\n[MIT](https://choosealicense.com/licenses/mit/).\n\n# Project status\n\nFollowing is a table of some updates regarding the project status. Note that these do not correspond to specific commits or milestones.\n\n| Date | Status | Notes or observations |\n|----------|:-------------:|----------------------|\n| June 27, 2025 | active | Successful remote deployments on Glama.AI and Smithery.AI. |\n| June 13, 2025 | active | Added LlamaIndex tool listing for demonstration only. (The `--all-extras` flag is necessary to install LlamaIndex, which is not installed by default.) |\n| June 9, 2025 | active | Added containerisation, support for self-signed, proxies. |\n| June 8, 2025 | active | Added dynamic composition. |\n| June 7, 2025 | active | Added tools to cover all the functionalities of the Frankfurter API. |\n| June 7, 2025 | active | Project started. |\n",
"bugtrack_url": null,
"license": null,
"summary": "A MCP server for currency exchange rates and currency conversion using the Frankfurter API.",
"version": "0.3.3",
"project_urls": {
"Download": "https://pypi.org/project/frankfurtermcp/",
"Issues": "https://github.com/anirbanbasu/frankfurtermcp/issues",
"Repository": "https://github.com/anirbanbasu/frankfurtermcp"
},
"split_keywords": [
"currency-converter",
" currency-exchange-rates",
" fastmcp",
" finance",
" frankfurter-api",
" mcp",
" mcp-composition",
" mcp-server",
" model-context-protocol",
" model-context-protocol-server"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "4a1a4c7b0a36035486c77ee9a7a76fadb1a318c38ee7e94e1d8f4119c8c3b85c",
"md5": "f3983a36ddd3edb2ccfe611cbdeefa69",
"sha256": "3b0b36428e101b9f131277554a04d1ef2b33548bb981a1470db5b3affcb1a7c2"
},
"downloads": -1,
"filename": "frankfurtermcp-0.3.3-py3-none-any.whl",
"has_sig": false,
"md5_digest": "f3983a36ddd3edb2ccfe611cbdeefa69",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.12",
"size": 16240,
"upload_time": "2025-08-01T01:11:37",
"upload_time_iso_8601": "2025-08-01T01:11:37.242597Z",
"url": "https://files.pythonhosted.org/packages/4a/1a/4c7b0a36035486c77ee9a7a76fadb1a318c38ee7e94e1d8f4119c8c3b85c/frankfurtermcp-0.3.3-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "fad376fb1e3496a2422d2a2b4f0db8bcf8236ac9281005a2322dfa44e2c70935",
"md5": "94927a5333512201c1ed87c61bccfece",
"sha256": "360d462d33cc0251eeba5bf2c56c204ece02fc9ec3a393135426588b36a7fd7b"
},
"downloads": -1,
"filename": "frankfurtermcp-0.3.3.tar.gz",
"has_sig": false,
"md5_digest": "94927a5333512201c1ed87c61bccfece",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.12",
"size": 2424893,
"upload_time": "2025-08-01T01:11:38",
"upload_time_iso_8601": "2025-08-01T01:11:38.335783Z",
"url": "https://files.pythonhosted.org/packages/fa/d3/76fb1e3496a2422d2a2b4f0db8bcf8236ac9281005a2322dfa44e2c70935/frankfurtermcp-0.3.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-08-01 01:11:38",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "anirbanbasu",
"github_project": "frankfurtermcp",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "frankfurtermcp"
}
JSON
