A
licenseNot graded
qualityD
maintenanceReal-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.
21
ISC
Frankfurter
Server Details
Convert currencies and fetch blended FX rates from 50+ institutional sources.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- lineofflight/frankfurter-mcp
- GitHub Stars
- 2
- Server Listing
- frankfurter-mcp
Available Tools
3 toolsconvertConvert currencyARead-onlyInspect
Convert an amount from one currency to another. Returns {amount, currency} rounded to the target's minor units. Upstream rounds rates per direction; for low-value sources, flip via get_rates for more precision.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ISO 4217 target currency. | |
| date | No | Date YYYY-MM-DD for a past rate; omit for latest. | |
| from | Yes | ISO 4217 source currency. | |
| amount | Yes | Amount in the source currency. Normalize localized input first: '100,50' -> 100.5; German '1.000,50' -> 1000.5; English '1,000.50' -> 1000.5. |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds significant behavioral context beyond annotations: it specifies rounding to target minor units, explains upstream rounding behavior per direction, and recommends flipping via get_rates for precision. This matches readOnlyHint and openWorldHint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loading the primary action and then providing precision details. Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple conversion tool with no output schema, the description covers return format (amount, currency, rounded) and provides precision guidance. It lacks error handling details but is sufficient given sibling tools and open world annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, baseline 3. The description adds value by explaining rounding behavior (target minor units) and includes detailed normalization examples for the amount parameter, clarifying input handling beyond schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Convert an amount from one currency to another,' providing a specific verb and resource. It distinguishes from siblings (get_rates, list_currencies) by focusing on conversion rather than rate retrieval or listing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises using get_rates for low-value sources to obtain more precision, giving clear context on when to choose an alternative. However, it does not fully elaborate on all alternative scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_ratesGet exchange ratesARead-onlyInspect
Latest or a single day's exchange rates. The raw-rate companion to convert.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | ISO 4217 base currency. Default EUR. | |
| date | No | Single day YYYY-MM-DD. Omit for the latest rates. | |
| quotes | No | ISO 4217 quote codes to return; omit for all. |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral context as a raw-rate companion and the ability to fetch latest or specific date rates, which is consistent and adds value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two short sentences, no unnecessary words, and front-loads the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity and good annotations/schema, the description covers purpose and sibling relation. It could optionally mention the output format (e.g., exchange rates map) but is not severely lacking.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with detailed parameter descriptions (ISO 4217, date format, etc.), so the tool description adds no additional parameter meaning, meeting the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it gets exchange rates (latest or single day) and explicitly distinguishes itself as the 'raw-rate companion to convert', differentiating from the sibling tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage via the 'raw-rate companion' hint, but does not provide explicit when-to-use or when-not-to-use guidance beyond the sibling 'convert'. It does not address the 'list_currencies' sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_currenciesList currenciesARead-onlyInspect
List all supported ISO 4217 currency codes and their full names (e.g. { 'USD': 'United States Dollar' }).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds format details beyond the annotations: it returns a mapping of code to name. Annotations already declare readOnlyHint and openWorldHint, which align. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with purpose, no fluff. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, full annotation coverage, and a simple return format described, the description is fully complete for this tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, and the schema coverage is 100% (empty). The description provides meaning about the output format, which is the only semantic needed. Baseline 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool lists all supported ISO 4217 currency codes with their full names, using a specific verb and resource. It distinguishes from siblings 'convert' and 'get_rates' by specifying enumeration rather than conversion or rate retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is used for retrieving the full set of supported currencies. While it does not explicitly state when not to use it or mention alternatives, the sibling context makes the usage clear. No exclusions are needed given the simple scope.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- Changed
convert2 fields changed- changed
Input schema / properties / amount / descriptionPrevious value: -"Amount in the source currency."New value: +"Amount in the source currency. Normalize localized input first: '100,50' -> 100.5; German '1.000,50' -> 1000.5; English '1,000.50' -> 1000.5." - changed
Input schema / properties / date / descriptionPrevious value: -"Historical date YYYY-MM-DD. Omit for latest."New value: +"Date YYYY-MM-DD for a past rate; omit for latest."
- Changed
get_rates5 fields changed- changed
Input schema / properties / date / descriptionPrevious value: -"Single day YYYY-MM-DD. Mutually exclusive with start/end."New value: +"Single day YYYY-MM-DD. Omit for the latest rates." - removed
Input schema / properties / endRemoved value: -{ - "$ref": "#/properties/date", - "description": "Range end YYYY-MM-DD (inclusive). Requires start and quotes." -} - removed
Input schema / properties / providersRemoved value: -{ - "description": "Provider keys. Omit for blended (default).", - "items": { - "type": "string" - }, - "type": "array" -} - changed
Input schema / properties / quotes / descriptionPrevious value: -"ISO 4217 quote codes. Required when start/end is set."New value: +"ISO 4217 quote codes to return; omit for all." - removed
Input schema / properties / startRemoved value: -{ - "$ref": "#/properties/date", - "description": "Range start YYYY-MM-DD (inclusive). Requires end and quotes." -}
- Added
list_currencies
2 tool updates
- First observed
convert - First observed
get_rates
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Convert currencies, get FX rates, and query historical ECB exchange rate data.
Live & historical FX rates and currency conversion for AI agents. No API keys.
Live & historical FX rates and currency conversion for AI agents. No API keys.
51Convert currencies on the daily European Central Bank reference rates. No API key, no signup.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceConvert currencies, get FX rates, and query historical ECB exchange rate data via MCP.3981Apache 2.0
- AlicenseAqualityDmaintenanceProvides currency conversion using the Wise API, supporting real-time and historical rates with caching and cross-rate calculation.2MIT
- FlicenseNot gradedqualityDmaintenanceProvides real-time and historical foreign exchange rates for 31+ currencies, enabling currency conversion, historical rate lookups, and time series analysis using data from the Frankfurter API.-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool has a distinct, non-overlapping purpose: convert handles amount conversion with rounding, get_rates provides raw exchange rates, and list_currencies enumerates supported currencies. No ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb or verb_noun pattern (convert, get_rates, list_currencies). The naming is predictable and uniform.
Tool Count5/5
Three tools are well-scoped for a currency exchange server: conversion, rate retrieval, and currency listing. The count is appropriate for the domain and avoids unnecessary complexity.
Completeness4/5
The tool set covers the core workflows: converting amounts, fetching rates, and listing currencies. Minor gaps exist, such as lack of historical rate time series, but the set is generally complete for typical usage.