Skip to main content
Glama
anirbanbasu

FrankfurterMCP

by anirbanbasu

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SSL_CERT_DIRNoSSL certificate directory path for self-signed certificates of hosted API endpoint or intermediate HTTP(S) proxy server(s).
FAST_MCP_HOSTNoThis 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_PORTNoThis variable specifies which port the MCP server must listen on unless the server transport (see below) is set to stdio.8000
HTTPX_TIMEOUTNoThe time for the underlying HTTP client to wait, in seconds, for a response from the Frankfurter API.5.0
SSL_CERT_FILENoSSL certificate file path for self-signed certificates of hosted API endpoint or intermediate HTTP(S) proxy server(s).
HTTPX_VERIFY_SSLNoThis 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_URLNoIf 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_TRANSPORTNoThe 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_RESPONSENoAn 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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_supported_currenciesA

Returns a list of three-letter currency codes for the supported currencies.

get_latest_exchange_ratesA

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.

greetC

A simple greeting tool to demonstrate middleware functionality.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have distinct purposes: conversion vs. rates vs. supported currencies. However, convert_currency_latest and get_latest_exchange_rates overlap slightly (both use latest rates), but descriptions clarify one is for conversion and the other for rates.

Naming Consistency4/5

Tool names mostly follow verb_noun pattern (e.g., convert_currency_latest, get_historical_exchange_rates). The greet tool breaks the pattern, but the rest are consistent and clear.

Tool Count4/5

Six tools cover core currency exchange functionality without being excessive. The greet tool is superfluous but doesn't ruin the scope.

Completeness4/5

Covers latest and historical rates, conversion on both latest and specific dates, and listing supported currencies. Missing batch conversion or currency metadata, but core workflows are complete.

Maintenance

ActivitySlowing
ResponsivenessWithin a week