Skip to main content
Glama
deenesjakoruzh
UniRate-API

UniRate MCP

Official
by UniRate-API
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Hybrid

UniRate MCP 服务器

npm License

这是一个用于 UniRate API 的 Model Context Protocol 服务器 —— 让 Claude、Cursor、Continue 以及任何兼容 MCP 的 AI 助手能够直接获取货币转换和汇率信息。

  • 🔄 170 多种货币（法币 + 主流加密货币）之间的实时转换

  • 📈 历史汇率可追溯至 1999 年（Pro 计划）

  • 🆓 免费层级，无需信用卡 —— 请在 unirateapi.com 获取密钥

  • 🧩 四个工具，完全类型化的输入（Zod 模式），结构化输出

  • 🌐 Stdio + 可流式传输的 HTTP/SSE 传输 —— 可本地运行或作为远程 MCP 端点托管

  • ⚡ 纯 Node 18+，仅依赖 @modelcontextprotocol/sdk

为什么需要这个

目前大多数“AI 货币”工作流要么涉及在自定义工具中手动编写 fetch 包装器，要么使用将原始 JSON 传给模型的通用 HTTP MCP 服务器。本服务器为模型提供了一个紧凑、类型化且具备货币感知能力的工具界面 —— 它们可以询问“2020-03-15 的 100 美元是多少欧元？”，并获得格式化的答案以及可链接到其他工具调用的结构化负载。

Related MCP server: FX Currency MCP Server

快速开始

1. 安装

npm install -g @unirate/mcp

或者使用 npx @unirate/mcp 按需运行（无需安装）。

2. 获取 UniRate API 密钥

免费层级涵盖 convert、latest_rate 和 list_currencies。请在 unirateapi.com 注册 —— 无需信用卡。

3. 将其接入你的 MCP 客户端

Claude Desktop

编辑 ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) 或 %APPDATA%\Claude\claude_desktop_config.json (Windows)：

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

重启 Claude Desktop。四个 UniRate 工具将出现在工具选择器中。

Cursor / Continue / Cline

添加到你的 MCP 配置中（.cursor/mcp.json、~/.continue/config.json 等）：

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

从源码运行

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. 作为远程端点运行（可流式传输的 HTTP / SSE）

默认情况下，服务器使用 stdio，这是 Claude Desktop 和大多数 MCP 客户端所需要的。若要将其作为远程端点托管（用于共享使用、多用户部署或基于浏览器的客户端），请以 HTTP 模式启动：

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

这将暴露：

  • POST /mcp — 可流式传输的 HTTP 端点（支持 SSE）。无状态：每个请求都会构建一个新的服务器，因此同一个进程可以服务多个并发客户端。

  • GET /healthz — JSON 存活探针 ({ "status": "ok", "server": "unirate-mcp", "version": "..." })。

将任何支持可流式传输 HTTP 的 MCP 客户端（支持远程服务器的 Claude Desktop、Cursor 远程 MCP 等）指向 http://your-host:3001/mcp。在生产环境中，请将其置于反向代理 + TLS 之后。

编程方式 / Edge 运行时（Cloudflare Workers、Deno、Bun）

该包导出了 buildServer(client)，因此你可以将其连接到你的运行时所偏好的任何传输方式。对于 Workers / Deno / Bun，请使用 SDK 的 webStandardStreamableHttp 传输方式配合导出的 buildServer 实例。

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

工具

convert

按最新汇率将金额从一种货币转换为另一种货币。

参数

类型

必填

说明

from

string

是

ISO 4217 代码 (例如 USD)

to

string

是

ISO 4217 代码 (例如 EUR)

amount

number

是

from 的正数金额

调用示例：

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

响应： 人类可读的文本加上结构化的 { from, to, amount, result }。

latest_rate

获取当前汇率。

参数

类型

必填

说明

from

string

是

基础货币

to

string

否

目标货币。省略以获取所有货币的汇率

historical_rate (Pro 计划)

获取特定日期生效的汇率。主要法币对的历史数据可追溯至 1999-01-04。

参数

类型

必填

说明

date

string

是

YYYY-MM-DD (例如 2020-03-15)

from

string

是

源货币

to

string

是

目标货币

amount

number

否

默认为 1

免费层级密钥会收到明确的错误提示，引导用户前往 unirateapi.com 进行升级。

list_currencies

返回支持的货币代码数组（170+），无需参数。适用于自动补全或验证用户提供的代码。

错误处理

所有 UniRate API 故障都会映射为友好的工具错误：

HTTP

错误类

模型看到的错误信息

400

InvalidRequestError

"Invalid request parameters"

401

AuthenticationError

"Missing or invalid API key"

403

ProPlanRequiredError

"…requires Pro… upgrade at https://unirateapi.com"

404

InvalidCurrencyError

"Currency not found or no data available"

429

RateLimitError

"Rate limit exceeded"

503

APIError

"Service unavailable"

网络/超时错误会被封装在 UnirateError 中。工具调用总是返回带有 isError: true 的响应对象，而不是抛出协议级别的错误，以便模型能够优雅地恢复。

开发

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

相关项目

UniRate 提供 9 种语言的官方客户端库：

以及一个 n8n 社区节点。

许可证

MIT — 详见 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
NameRequiredDescriptionDefault
fromYesSource currency code, e.g. 'USD'
toYesTarget currency code, e.g. 'EUR'
amountYesAmount 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
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format, e.g. '2020-03-15'
fromYesSource currency code
toYesTarget currency code
amountNoOptional 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
NameRequiredDescriptionDefault
fromYesBase currency code, e.g. 'USD'
toNoOptional 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
NameRequiredDescriptionDefault

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.

  1. 4 tool updatesv0.2.2
    • 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 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

Related MCP Connectors

Related MCP Servers

  • Frankfurter MCP

    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.
    5
    MIT

  • FX Currency MCP Server

    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.
    -

  • Realtime Exchange Rate MCP

    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.
    4
    130 npm
    MIT

  • exchangerate

    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.
    148 npm
    MIT