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 서버

npm License

UniRate API를 위한 Model Context Protocol 서버입니다. Claude, Cursor, Continue 및 모든 MCP 호환 AI 어시스턴트에게 통화 변환 및 환율에 대한 일류 수준의 액세스 권한을 제공합니다.

🔄 170개 이상의 통화(법정 화폐 + 주요 암호화폐) 간 실시간 변환
📈 1999년부터의 과거 환율(Pro 플랜)
🆓 무료 티어 제공, 신용카드 불필요 — unirateapi.com에서 키 발급 가능
🧩 4가지 도구, 완벽하게 타입이 지정된 입력(Zod 스키마), 구조화된 출력
🌐 Stdio + Streamable HTTP/SSE 전송 — 로컬에서 실행하거나 원격 MCP 엔드포인트로 호스팅 가능
⚡ 순수 Node 18+ 환경, @modelcontextprotocol/sdk에 대한 단일 의존성

이 서버가 필요한 이유

오늘날 대부분의 "AI용 통화" 워크플로우는 사용자 지정 도구에서 직접 만든 fetch 래퍼를 사용하거나, 모델에 원시 JSON을 전달하는 일반적인 HTTP MCP 서버를 사용합니다. 이 서버는 모델에 간결하고 타입이 지정된, 통화 인식 도구 인터페이스를 제공합니다. 모델이 "2020년 3월 15일 기준 100 USD는 몇 EUR인가요?"라고 물으면, 형식화된 답변과 다른 도구 호출에 연결할 수 있는 구조화된 페이로드를 반환합니다.

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을 재시작하세요. 도구 선택기에 4개의 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. 원격 엔드포인트로 실행 (Streamable HTTP / SSE)

기본적으로 서버는 Claude Desktop 및 대부분의 MCP 클라이언트가 요구하는 stdio를 사용합니다. 공유 사용, 다중 사용자 배포 또는 브라우저 기반 클라이언트를 위해 원격 엔드포인트로 호스팅하려면 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 — Streamable HTTP 엔드포인트(SSE 지원). 상태 비저장: 요청마다 새로운 서버가 생성되므로 동일한 프로세스로 많은 동시 클라이언트를 처리할 수 있습니다.
GET /healthz — JSON 라이브니스 프로브({ "status": "ok", "server": "unirate-mcp", "version": "..." }).

Streamable-HTTP 지원 MCP 클라이언트(원격 서버 지원 Claude Desktop, Cursor 원격 MCP 등)를 http://your-host:3001/mcp로 지정하세요. 프로덕션 환경에서는 리버스 프록시 + TLS 뒤에 배치하세요.

프로그래밍 방식 / 엣지 런타임 (Cloudflare Workers, Deno, Bun)

패키지는 buildServer(client)를 내보내므로 런타임이 선호하는 전송 방식에 연결할 수 있습니다. Workers / Deno / Bun의 경우, 내보낸 buildServer 인스턴스와 함께 SDK의 webStandardStreamableHttp 전송을 사용하세요.

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년 1월 4일까지의 데이터를 지원합니다.

매개변수	타입	필수	참고
`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`	"잘못된 요청 매개변수"
401	`AuthenticationError`	"API 키가 없거나 잘못됨"
403	`ProPlanRequiredError`	"…Pro 플랜 필요… https://unirateapi.com에서 업그레이드"
404	`InvalidCurrencyError`	"통화를 찾을 수 없거나 데이터 없음"
429	`RateLimitError`	"요청 제한 초과"
503	`APIError`	"서비스 이용 불가"

네트워크/타임아웃 오류는 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

라이선스

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

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 서버

이 서버가 필요한 이유

빠른 시작

1. 설치

2. UniRate API 키 발급

3. MCP 클라이언트에 연결

Claude Desktop

Cursor / Continue / Cline

소스에서 실행

4. 원격 엔드포인트로 실행 (Streamable HTTP / SSE)

프로그래밍 방식 / 엣지 런타임 (Cloudflare Workers, Deno, Bun)

도구

convert

latest_rate

historical_rate (Pro 플랜)

list_currencies

오류

개발

관련 프로젝트

라이선스

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

`convert`

`latest_rate`

`historical_rate` (Pro 플랜)

`list_currencies`