de en es ja ko ru zh

UniRate MCP

Name: UniRate MCP
Author: UniRate-API

Official

by UniRate-API

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Hybrid

UniRate MCP-Server

npm License

Ein Model Context Protocol-Server für die UniRate API – geben Sie Claude, Cursor, Continue und jedem MCP-kompatiblen KI-Assistenten erstklassigen Zugriff auf Währungsumrechnung und Wechselkurse.

🔄 Echtzeit-Umrechnung zwischen über 170 Währungen (Fiat + wichtige Kryptowährungen)
📈 Historische Kurse bis 1999 (Pro-Plan)
🆓 Kostenlose Stufe, keine Kreditkarte erforderlich – holen Sie sich einen Schlüssel unter unirateapi.com
🧩 Vier Tools, vollständig typisierte Eingaben (Zod-Schemas), strukturierte Ausgaben
🌐 Stdio + Streamable HTTP/SSE-Transporte – lokal ausführen oder als Remote-MCP-Endpunkt hosten
⚡ Reines Node 18+, einzige Abhängigkeit von @modelcontextprotocol/sdk

Warum gibt es das?

Die meisten "Währungs-für-KI"-Workflows beinhalten heute manuell erstellte Fetch-Wrapper in benutzerdefinierten Tools oder generische HTTP-MCP-Server, die dem Modell rohes JSON übergeben. Dieser Server bietet Modellen eine kompakte, typisierte, währungsbewusste Tool-Oberfläche – sie fragen "Was waren 100 USD in EUR am 15.03.2020?" und erhalten eine formatierte Antwort sowie eine strukturierte Nutzlast, die sie in andere Tool-Aufrufe einbinden können.

Related MCP server: FX Currency MCP Server

Schnellstart

1. Installation

npm install -g @unirate/mcp

Oder führen Sie es bei Bedarf mit npx @unirate/mcp aus (keine Installation).

2. UniRate API-Schlüssel abrufen

Die kostenlose Stufe deckt convert, latest_rate und list_currencies ab. Registrieren Sie sich unter unirateapi.com – keine Kreditkarte erforderlich.

3. In Ihren MCP-Client einbinden

Claude Desktop

Bearbeiten Sie ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) oder %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "unirate": {
      "command": "npx",
      "args": ["-y", "@unirate/mcp"],
      "env": {
        "UNIRATE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Starten Sie Claude Desktop neu. Die vier UniRate-Tools erscheinen in der Tool-Auswahl.

Cursor / Continue / Cline

Fügen Sie es zu Ihrer MCP-Konfiguration hinzu (.cursor/mcp.json, ~/.continue/config.json usw.):

{
  "mcpServers": {
    "unirate": {
      "command": "npx",
      "args": ["-y", "@unirate/mcp"],
      "env": { "UNIRATE_API_KEY": "your-api-key-here" }
    }
  }
}

Aus dem Quellcode

git clone https://github.com/UniRate-API/unirate-mcp.git
cd unirate-mcp
npm install && npm run build
UNIRATE_API_KEY=your-key node dist/index.js

4. Als Remote-Endpunkt ausführen (Streamable HTTP / SSE)

Standardmäßig verwendet der Server stdio, was Claude Desktop und die meisten MCP-Clients erwarten. Um ihn stattdessen als Remote-Endpunkt zu hosten – für die gemeinsame Nutzung, Multi-User-Bereitstellungen oder browserbasierte Clients – starten Sie ihn im HTTP-Modus:

UNIRATE_API_KEY=your-key unirate-mcp --http 3001
# or via env:
UNIRATE_API_KEY=your-key UNIRATE_MCP_HTTP_PORT=3001 unirate-mcp

Das stellt Folgendes bereit:

POST /mcp – Streamable HTTP-Endpunkt (SSE-fähig). Zustandslos: Ein neuer Server wird pro Anfrage erstellt, sodass derselbe Prozess viele gleichzeitige Clients bedienen kann.
GET /healthz – JSON-Liveness-Probe ({ "status": "ok", "server": "unirate-mcp", "version": "..." }).

Verweisen Sie jeden Streamable-HTTP-fähigen MCP-Client (Claude Desktop mit Remote-Server-Unterstützung, Cursor Remote-MCP usw.) auf http://your-host:3001/mcp. Platzieren Sie es für die Produktion hinter einen Reverse-Proxy + TLS.

Programmatische / Edge-Runtimes (Cloudflare Workers, Deno, Bun)

Das Paket exportiert buildServer(client), sodass Sie es mit jedem Transport verbinden können, den Ihre Runtime bevorzugt. Verwenden Sie für Workers / Deno / Bun den webStandardStreamableHttp-Transport des SDKs mit einer exportierten buildServer-Instanz.

import { UnirateClient } from "@unirate/mcp/dist/client.js";
import { buildServer } from "@unirate/mcp";
// → connect to your runtime's preferred transport

Tools

`convert`

Rechnet einen Betrag zum aktuellen Kurs von einer Währung in eine andere um.

Parameter	Typ	Erforderlich	Hinweise
`from`	string	ja	ISO 4217-Code (z. B. `USD`)
`to`	string	ja	ISO 4217-Code (z. B. `EUR`)
`amount`	number	ja	Positiver Betrag in `from`

Beispielaufruf:

{ "name": "convert", "arguments": { "from": "USD", "to": "EUR", "amount": 100 } }

Antwort: menschenlesbarer Text plus strukturiertes { from, to, amount, result }.

`latest_rate`

Aktuellen Wechselkurs(e) abrufen.

Parameter	Typ	Erforderlich	Hinweise
`from`	string	ja	Basiswährung
`to`	string	nein	Ziel. Weglassen, um Kurse für alle Währungen zu erhalten

`historical_rate` (Pro-Plan)

Ruft den Wechselkurs ab, der an einem bestimmten Datum gültig war. Abdeckung bis zum 04.01.1999 für wichtige Fiat-Paare.

Parameter	Typ	Erforderlich	Hinweise
`date`	string	ja	`YYYY-MM-DD` (z. B. `2020-03-15`)
`from`	string	ja	Quellwährung
`to`	string	ja	Zielwährung
`amount`	number	nein	Standardwert ist 1

Schlüssel der kostenlosen Stufe erhalten eine klare Fehlermeldung mit Verweis auf unirateapi.com für ein Upgrade.

`list_currencies`

Gibt das Array der unterstützten Währungscodes (170+) ohne Parameter zurück. Nützlich für die Autovervollständigung oder die Validierung vom Benutzer bereitgestellter Codes.

Fehler

Alle UniRate API-Fehler werden auf benutzerfreundliche Tool-Fehler abgebildet:

HTTP	Fehlerklasse	Was das Modell sieht
400	`InvalidRequestError`	"Ungültige Anfrageparameter"
401	`AuthenticationError`	"Fehlender oder ungültiger API-Schlüssel"
403	`ProPlanRequiredError`	"…erfordert Pro… Upgrade unter https://unirateapi.com"
404	`InvalidCurrencyError`	"Währung nicht gefunden oder keine Daten verfügbar"
429	`RateLimitError`	"Ratenlimit überschritten"
503	`APIError`	"Dienst nicht verfügbar"

Netzwerk-/Timeout-Fehler werden in UnirateError gekapselt. Tool-Aufrufe geben immer ein Antwortobjekt mit isError: true zurück, anstatt Fehler auf Protokollebene auszulösen, sodass das Modell sich ordnungsgemäß erholen kann.

Entwicklung

npm install
npm run build       # compile TypeScript to dist/
npm test            # 24 mock tests
UNIRATE_LIVE=1 UNIRATE_API_KEY=... npm run test:live  # +4 live free-tier tests

Lizenz

MIT – siehe LICENSE.

Available Tools

4 tools

convertConvert currencyA

Read-only

Convert an amount from one currency to another using the latest exchange rate. Codes are ISO 4217 (e.g. USD, EUR, GBP). Supports 170+ fiat currencies and major cryptocurrencies.

ParametersJSON Schema

Name	Required	Description
`from`	Yes	Source currency code, e.g. 'USD'
`to`	Yes	Target currency code, e.g. 'EUR'
`amount`	Yes	Amount in the source currency

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint and openWorldHint. The description adds that it uses the latest exchange rate and supports 170+ fiat and crypto currencies with ISO 4217 codes, which is helpful context beyond the annotations.

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?

Two sentences, front-loaded, no redundant words. Every sentence adds value: first explains action, second defines scope and standard.

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 tool's simplicity and lack of output schema, the description covers core function, supported currencies, and code standard. Could mention precision or source but not necessary for basic use.

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 descriptions for all three parameters. The description does not add new information about individual parameters beyond the schema's examples and hints; baseline is 3.

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 uses specific verb 'convert' and identifies resource as currency amount using latest rate. It clearly distinguishes from sibling tools like historical_rate and list_currencies by focusing on conversion rather than rate lookup 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for converting amounts, but does not explicitly state when to use it versus alternatives like latest_rate (for rate only) or historical_rate. No when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

historical_rateGet historical exchange rate (Pro plan required)A

Read-only

Fetch the exchange rate that was in effect on a specific date. Date format YYYY-MM-DD. Coverage goes back to 1999-01-04 for major fiat pairs. Requires UniRate Pro — free-tier keys will receive a clear upgrade-required error.

ParametersJSON Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format, e.g. '2020-03-15'
`from`	Yes	Source currency code
`to`	Yes	Target currency code
`amount`	No	Optional amount to convert at the historical rate. Defaults to 1.

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide readOnlyHint and openWorldHint; description adds coverage start date (1999-01-04) and error behavior for free-tier keys. Does not disclose behavior for out-of-range dates or missing data, but key behavioral context is added beyond annotations.

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?

Three sentences: first states purpose, second gives format, third adds coverage and requirement. No wasted words, front-loaded with action verb. Perfect structure for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks description of return value (e.g., what is returned if amount is provided). No output schema, so description should hint at response shape. Also, does not specify behavior for missing or invalid dates beyond coverage range. Completeness is adequate but has notable gaps.

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 has 100% coverage with clear descriptions. Description adds value by stating the coverage start date for the date parameter, which is not in schema. Also reinforces date format. Does not add to other parameters, but schema already sufficient.

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 it fetches the exchange rate for a specific date, using strong verb 'Fetch' and specific resource. Differentiates from siblings (convert, latest_rate, list_currencies) by focusing on historical data. Mentions date format and coverage range, solidifying purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly notes that the tool requires UniRate Pro, including that free-tier keys will receive an error. This is a critical usage condition. Also provides date format and coverage range, helping decide when to use. Does not need to list alternatives as purpose is self-evident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

latest_rateGet latest exchange rate(s)A

Read-only

Fetch the latest exchange rate for a base currency. If 'to' is provided, returns a single rate; otherwise returns rates for all supported currencies relative to the base.

ParametersJSON Schema

Name	Required	Description	Default
`from`	Yes	Base currency code, e.g. 'USD'
`to`	No	Optional target currency. Omit to get rates for all currencies.

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint and openWorldHint. Description adds scoping (base currency, single/all rates) but doesn't elaborate on data freshness, caching, or external dependencies. Adequate given annotation coverage.

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?

Two sentences, front-loads the main action, no unnecessary words. Perfectly concise while conveying the two use cases.

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 low complexity (2 params, no output schema), description is mostly complete. Could briefly mention return format (e.g., object with rates) but not essential. Agent can infer from typical usage.

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 already describes both params clearly (100% coverage). Description adds value by explaining the behavioral switch when 'to' is omitted, which is not in the schema descriptions. Enhances understanding.

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?

Clearly states 'Fetch the latest exchange rate' with distinct behaviors: single rate if 'to' provided, all rates if omitted. Differentiates from siblings through scope (latest vs. historical, conversion, currency list).

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?

Describes when to provide 'to' vs omit, but does not explicitly compare to sibling tools like convert or historical_rate. Agent can infer from sibling names, but no direct usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_currenciesList supported currenciesA

Read-only

Return the list of currency codes supported by the UniRate API (170+ fiat plus major crypto).

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?

Annotations already indicate readOnlyHint and openWorldHint; the description adds the count and types of currencies, providing useful context beyond the annotations.

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 a single sentence that is direct and front-loaded, with no unnecessary words.

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 no parameters and no output schema, the description fully informs the agent about the tool's purpose and output.

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?

No parameters exist, so the schema covers 100%; baseline for zero parameters is 4, and the description omits irrelevant parameter details.

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 'Return the list of currency codes' and specifies the scope '170+ fiat plus major crypto', distinguishing it from sibling tools for conversion and rates.

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?

While no explicit when-to-use guidance is given, the simple nature and clear context make it obvious this tool is for obtaining supported currencies before using other tools.

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.

4 tool updatesv0.2.2May 6, 2026
- First observedconvert
- First observedhistorical_rate
- First observedlatest_rate
- First observedlist_currencies

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored 2026-05-06 06:10 across 4 tools

Disambiguation5/5

Each tool serves a distinct purpose: converting amounts, fetching historical rates, getting latest rates, and listing supported currencies. No overlaps.

Naming Consistency5/5

All tool names use consistent snake_case and follow a verb_noun or adjective_noun pattern, making them predictable.

Tool Count5/5

4 tools is well-scoped for a currency conversion API, covering essential operations without unnecessary complexity.

Completeness5/5

The tool set covers conversion, latest rates, historical rates, and currency listing—no obvious gaps for the domain.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

Market Intel MCP A
com.datakoot
Live & historical FX rates and currency conversion for AI agents. No API keys.
Finance Open Data
51
Market Intel MCP A
io.github.selflabbs
Live & historical FX rates and currency conversion for AI agents. No API keys.
Finance Cryptocurrency
2
FX Converter MCP A
io.github.Lulu-The-Narwhal
Free, keyless real-time currency conversion and exchange rates for any currency pair.
Finance Open Data
21
Currency & Exchange Rate MCP A
io.github.FoundryNet
Currency conversion + exchange rates: free convert/rates, paid historical & trend analytics.
Finance Research & Data
2

Related MCP Servers

Frankfurter MCP
Finance Search Open Data
jessicayanwang
A
license
A
quality
D
maintenance
Provides access to currency exchange rates and conversion tools using the Frankfurter API, including latest rates, historical data, and time series from sources like the European Central Bank.
Updated a year ago (2025-09-30 02:02 UTC)
5
MIT
FX Currency MCP Server
Finance Search Open Data
pavm035
F
license
Not graded
quality
D
maintenance
Provides 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.
Updated 9 months ago (2025-12-24 23:41 UTC)
-
Realtime Exchange Rate MCP
Finance
AllRates-Today
A
license
A
quality
B
maintenance
Provides real-time foreign-exchange rates, historical data, and multi-currency lookups to MCP-compatible AI coding assistants like Claude Code and Cursor.
Updated a month ago (2026-08-31 20:36 UTC)
4
130 npm
MIT
exchangerate
Finance Open Data
pipeworx-io
A
license
Not graded
quality
B
maintenance
Provides real-time exchange rates for any currency pair using open.er-api.com, simplifying currency conversion with a single tool.
Updated 3 days ago (2026-09-26 12:21 UTC)
148 npm
MIT

UniRate MCP-Server

Warum gibt es das?

Schnellstart

1. Installation

2. UniRate API-Schlüssel abrufen

3. In Ihren MCP-Client einbinden

Claude Desktop

Cursor / Continue / Cline

Aus dem Quellcode

4. Als Remote-Endpunkt ausführen (Streamable HTTP / SSE)

Programmatische / Edge-Runtimes (Cloudflare Workers, Deno, Bun)

Tools

convert

latest_rate

historical_rate (Pro-Plan)

list_currencies

Fehler

Entwicklung

Verwandte Projekte

Lizenz

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

`convert`

`latest_rate`

`historical_rate` (Pro-Plan)

`list_currencies`