# CurrencyCore (remote · mcp.currency-core.com)

Live FX rates, conversion, IMF PPP, and historical currency analytics.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.currency-core.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/currencycore-currency-core-mcp/mcp.md), [page](https://verifymcp.io/servers/currencycore-currency-core-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.currency-core.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 4944 tokens (~89/item across 55 items; 14 tools + 41 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (86% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CurrencyCore MCP server?

CurrencyCore is a hosted endpoint at https://mcp.currency-core.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http currencycore-currency-core-mcp 'https://mcp.currency-core.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "currencycore-currency-core-mcp": {
      "url": "https://mcp.currency-core.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "currencycore-currency-core-mcp": {
      "type": "http",
      "url": "https://mcp.currency-core.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.currencycore-currency-core-mcp]
url = "https://mcp.currency-core.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "currencycore-currency-core-mcp": {
      "type": "remote",
      "url": "https://mcp.currency-core.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add currencycore-currency-core-mcp --url 'https://mcp.currency-core.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  currencycore-currency-core-mcp:
    url: "https://mcp.currency-core.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "currencycore-currency-core-mcp": {
      "Transport": "http",
      "Url": "https://mcp.currency-core.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add currencycore-currency-core-mcp -t streamable-http -u 'https://mcp.currency-core.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "currencycore-currency-core-mcp": {
      "type": "http",
      "url": "https://mcp.currency-core.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +1)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

### 2026-11-20 (score 78, 0)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

### 2026-11-19 (score 78, +1)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

### 2026-11-18 (score 77, 0)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

### 2026-11-17 (score 77, +1)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

### 2026-11-16 (score 76, 0)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

### 2026-11-15 (score 76, +1)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

### 2026-11-14 (score 75, 0)

- [security] Resource “openapi” now points somewhere else: mcp://docs/openapi → currencycore://openapi.json

## MCP tools (14)

### `list_countries` (~98 tokens)

Country reference

Return the supported countries and their official currencies as an array of `{ code, name, currencies }`. Use to resolve a country name to its ISO alpha-3 code before `get_ppp_factor` or `analyze_ppp`, or to check which countries are covered. Use `list_currencies` for currency codes. Returns the full list in one call and takes no parameters. Public tool: no sign-in and no API request billed.

### `list_currencies` (~121 tokens)

Currency reference

Return the full ISO 4217 currency catalogue as an array of `{ code, numeric, name, symbol }`. Use to resolve a currency name or symbol to its code, or to confirm a currency is supported before calling another tool, so a typo fails at selection rather than silently. Use `list_countries` for country codes. Non-ISO codes CNH, GGP, IMP, and JEP have an empty `numeric`. Returns the full list in one call and takes no parameters. Public tool: no sign-in and no API request billed.

### `convert` (~437 tokens)

Convert currency

Convert an amount from one currency to one or more targets at the reference rate for `date`, optionally PPP-adjusted. Use for any single-pair or amount conversion (for example "100 USD to EUR"). Use `get_rates`/`get_rates_by_base` for a full rate table, `get_history` for a series, and the `analyze_*` tools for statistics. `amount` defaults to 1 (each result then equals the rate); `ppp=true` applies purchasing-power parity and needs `CUR:COUNTRY` when a currency is used in more than one country; `date` must be today or earlier and defaults to the latest rate date. Returns `{ from, amount, date, results[] }`, each result carrying `result`, `rate`, and an optional `ppp` block. Invalid codes or dates return a 4xx error; no rate for the date is a 404. Requires a signed-in connection; each successful call bills 1 API request.

Input parameters:

- `amount` (number): Amount to convert. Optional, defaults to 1 (so each result equals the rate). When provided it must be a finite positive number.
- `date` (string): Rate date in YYYY-MM-DD (UTC). Must not be in the future. Defaults to latest.
- `from` (string, required): Source currency (ISO 4217), e.g. USD. For PPP (ppp=true), pass CUR:COUNTRY (e.g. USD:USA) when the currency is used in more than one country; common currencies are resolved automatically.
- `ppp` (boolean): When true, apply a PPP adjustment. Pass CUR:COUNTRY for currencies used in more than one country; common currencies (USD, EUR, INR and others) resolve automatically.
- `to` (string, required): One or more target currencies, comma-separated, e.g. EUR,INR (max 25). For PPP, pass CUR:COUNTRY pairs (e.g. EUR:DEU,INR:IND) when a currency is used in more than one country; common currencies are r…

Output parameters:

- `amount` (number)
- `asOf` (object)
- `date` (string)
- `from` (string)
- `fromCountry` (string)
- `message` (string)
- `requestedDate` (string)
- `results` (array)

### `get_rates` (~158 tokens)

Exchange rates (USD base)

Return the full USD-based exchange-rate snapshot for one date: `rates` maps every supported currency to units per 1 USD. Use when the user wants a multi-currency table in USD (for example "today's rates"). Use `get_rates_by_base` for a non-USD base, `convert` for one pair or amount, and `get_history` for a time series. Omitting `date` returns the latest available snapshot, which is not necessarily today. Returns `{ base: "USD", date, rates }`; a date with no snapshot is a 404. Requires a signed-in connection; each successful call bills 1 API request.

Input parameters:

- `date` (string): YYYY-MM-DD. Defaults to the latest available date.

Output parameters:

- `asOf` (object)
- `base` (string)
- `date` (string)
- `rates` (object)
- `requestedDate` (string)

### `get_rates_by_base` (~190 tokens)

Exchange rates by base currency

Return the daily FX snapshot re-based to `base`: every supported currency quoted as units per 1 unit of `base`, with `base` itself at 1. Use when the user wants a multi-currency table in a non-USD base (for example "rates in EUR"). Use `get_rates` for the USD table, `convert` for one pair or amount, and `get_history` for a time series. Omitting `date` returns the latest available snapshot, which is not necessarily today. Returns `{ base, date, rates }`; an unsupported base or a date with no snapshot is a 404. Requires a signed-in connection; each successful call bills 1 API request.

Input parameters:

- `base` (string, required): Base currency (3-letter ISO 4217), e.g. EUR.
- `date` (string): YYYY-MM-DD. Defaults to the latest available date.

Output parameters:

- `asOf` (object)
- `base` (string)
- `date` (string)
- `ppp` (object)
- `rates` (object)
- `requestedDate` (string)

### `get_history` (~335 tokens)

Currency rate history

Return one currency's rate series over a date range, expressed against `base`: `rates` maps each date (or aggregated period) to units of `currency` per 1 `base`. Use for a line chart or raw daily/weekly/monthly/yearly points for one currency. Use `analyze_history` for computed change, trend, and movers; use `convert` or `get_rates` for a single value or snapshot. Defaults: `to` today, `from` 7 days earlier, `base` USD, `interval` daily; coarser intervals average the daily rates per bucket. Returns `{ currency, base, interval, from, to, rates }`. Free plans are limited to the last 30 days; an invalid code or missing history is a 404. Requires a signed-in connection; each successful call bills 1 API request.

Input parameters:

- `base` (string): Base currency the rates are expressed against (3-letter ISO 4217). Defaults to USD.
- `currency` (string, required): The currency whose history to fetch (3-letter ISO 4217), e.g. INR. One currency per call.
- `from` (string): Start date YYYY-MM-DD (UTC). Defaults to 7 days before `to`.
- `interval` (string): Aggregation: daily (default), weekly, monthly, or yearly. Coarser intervals average the daily rates per bucket (weekly key = the week's Monday, monthly = YYYY-MM, yearly = YYYY).
- `to` (string): End date YYYY-MM-DD (UTC). Defaults to today; a future date clamps to today.

Output parameters:

- `base` (string)
- `currency` (string)
- `from` (string)
- `interval` (string)
- `rates` (object)
- `to` (string)

### `analyze_history` (~526 tokens)

History analysis (change, trend, movers)

Summarise how currencies moved against `base` over a window: start/end rate, change %, strengthened % (positive = stronger vs base), and optional min/max/avg. Use for questions like "how did EUR do over 10 years" and for movers rankings. Omit `currencies` to rank the universe (movers mode); provide them to compare specific ones. Use `get_history` for raw points, and the other `analyze_*` tools for volatility, correlation, drawdown, safe-haven, or mean-reversion questions. Defaults: 20-year window, `base` USD, `sort` strengthened, `assetClass` fiat, `limit` 10, `stats` true. Returns `{ base, from, to, mode, sort?, assetClass?, stats, results[] }`. A 404 means no rate data at the window edges. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

Input parameters:

- `assetClass` (string): Movers universe: fiat (default, liquid tradeable currencies), metals (XAU/XAG/XPT/XPD), all (every currency including illiquid/frontier), or crypto (accepted, but this FX dataset has no crypto data,…
- `base` (string): Currency everything is measured against (3-letter ISO 4217). Defaults to USD.
- `currencies` (string): Comma-separated currencies to compare, e.g. GBP,EUR,AED. OMIT to rank ALL currencies vs base ('movers' mode).
- `from` (string): Window start YYYY-MM-DD (UTC). Defaults to 20 years (2 decades) before `to`. See `period` for a shorthand.
- `interval` (string): Attach a trend series per named currency: weekly, monthly, or yearly (compare mode only).
- `limit` (number): Movers: how many top results to return (default 10, max 200).
- `period` (string): Relative window shorthand for `from`: e.g. 10y, 6m, 30d, ytd, max. Ignored if `from` is given.
- `sort` (string): Movers ranking: strengthened (default) or weakened.
- `stats` (boolean): Include min/max/avg over the window per currency. Defaults to true; pass false to skip.
- `to` (string): Window end YYYY-MM-DD (UTC). Defaults to today; a future date clamps to today.

Output parameters:

- `assetClass` (string)
- `base` (string)
- `from` (string)
- `interval` (string)
- `mode` (string)
- `results` (array)
- `sort` (string)
- `stats` (boolean)
- `to` (string)

### `get_ppp_factor` (~200 tokens)

PPP conversion factor

Return the IMF World Economic Outlook PPP conversion factor for one country and year: local currency units per international dollar. Use when the user needs the raw multiplier for one country/year, for example a cost-of-living comparison. Use `convert` with `ppp=true` to price an amount, and `analyze_ppp` for change over time or a cross-country ranking. `year` defaults to the latest configured PPP year (2024). Returns `{ year, countryCode, pppFactor, projected }`; `projected: true` marks an IMF projection rather than observed data. An unknown country or year is a 404. Requires a signed-in connection; each successful call bills 1 API request.

Input parameters:

- `country` (string, required): Country as an ISO 3166-1 alpha-3 code (e.g. IND).
- `year` (number): Four-digit year. Defaults to the configured current PPP year (2024).

Output parameters:

- `countryCode` (string)
- `pppFactor` (number)
- `projected` (boolean)
- `year` (number)

### `analyze_ppp` (~399 tokens)

PPP analysis (change, compare, movers)

Measure how a country's IMF PPP conversion factor changed over a year window: start/end year and factor, % change, and optional min/max/avg. Use for purchasing-power trends and cross-country PPP rankings. Omit `countries` to rank all countries (movers); provide ISO alpha-3 codes to compare specific ones. Use `get_ppp_factor` for a single country/year value, and `convert` with `ppp=true` to price an amount. Defaults: 10-year window, `sort` increased, `limit` 10, `stats` true. Returns `{ from, to, mode, stats, results[] }`, with `projected: true` marking an IMF projection. Returns an error when no PPP data exists in the window. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

Input parameters:

- `countries` (string): Comma-separated ISO 3166-1 alpha-3 country codes to compare, e.g. IND,DEU,USA. OMIT to rank ALL countries by PPP-factor change ('movers' mode).
- `from` (string): Window start YEAR (e.g. 2015). Defaults to 10 years before `to`. See `period` for a shorthand.
- `limit` (number): Movers: how many top results to return (default 10, max 200).
- `period` (string): Relative window shorthand for `from`: e.g. 10y, 20y, max. Ignored if `from` is given.
- `sort` (string): Movers ranking: increased (PPP factor rose most, default) or decreased.
- `stats` (boolean): Include min/max/avg of the PPP factor over the window per country. Defaults to true; pass false to skip.
- `to` (string): Window end YEAR (e.g. 2024). Defaults to the current year.

Output parameters:

- `from` (number)
- `mode` (string)
- `results` (array)
- `sort` (string)
- `stats` (boolean)
- `to` (number)

### `analyze_volatility` (~367 tokens)

Volatility analysis

Return annualized volatility (%) for each currency against `base`, with the number of daily returns used. Use to rank stability or find the most volatile currency or pair. Omit `currency` to rank the universe (`sort` stable or volatile); provide one currency or a comma-separated list to compare. Use `analyze_drawdown` for worst peak-to-trough loss and `analyze_safe_haven` for crisis resilience. Defaults: 365-day window, `base` USD, `sort` stable, `universe` liquid, `limit` 10. Returns `{ base, from, to, mode, basis, results[] }`; `volatility` is null when there is too little data. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

Input parameters:

- `base` (string): Base currency to measure against (3-letter ISO 4217). Defaults to USD.
- `currency` (string): Currency to measure (3-letter ISO 4217), or a comma-separated list to compare. OMIT to RANK the liquid-currency set by stability.
- `from` (string): Window start YYYY-MM-DD (UTC). Defaults to 365 days before `to`.
- `limit` (number): Ranking: how many to return (default 10, max 50).
- `sort` (string): Ranking direction: stable (least volatile first, default) or volatile.
- `to` (string): Window end YYYY-MM-DD (UTC). Defaults to today; a future date clamps to today.
- `universe` (string): Ranking universe: liquid (default, broad set) or majors (USD/EUR/GBP/JPY/CHF/CAD/AUD/NZD). Use majors for 'most volatile major pair'.

Output parameters:

- `base` (string)
- `basis` (string)
- `from` (string)
- `mode` (string)
- `results` (array)
- `sort` (string)
- `to` (string)
- `universe` (string)

### `analyze_correlation` (~251 tokens)

Correlation analysis

Return the Pearson correlation of each currency's daily returns with `base` over a window (−1..1), plus the number of overlapping observations. Use for diversification or co-movement questions such as "does CHF track EUR?". `currencies` is required and comma-separated; a non-USD `base` is usually more meaningful. Use `analyze_volatility` for dispersion and `analyze_history` for raw change. Defaults: 365-day window ending today. Returns `{ base, from, to, results[] }`; `correlation` is null when it is undefined for the window. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

Input parameters:

- `base` (string): Reference currency to correlate against (3-letter ISO 4217). Defaults to USD (a non-USD base is more meaningful).
- `currencies` (string, required): Comma-separated currencies to correlate with `base`, e.g. GBP,CHF,SEK.
- `from` (string): Window start YYYY-MM-DD (UTC). Defaults to 365 days before `to`.
- `to` (string): Window end YYYY-MM-DD (UTC). Defaults to today.

Output parameters:

- `base` (string)
- `from` (string)
- `results` (array)
- `to` (string)

### `analyze_drawdown` (~350 tokens)

Drawdown analysis

Return the worst peak-to-trough decline of each currency vs `base`, with peak, trough, and recovery dates/days. Use for "how far did it fall and did it recover" questions or to rank the deepest drawdowns. Omit `currency` to rank the universe (`sort` deepest or recovery); provide one currency or a list to compare. Use `analyze_volatility` for dispersion and `analyze_safe_haven` for crisis behaviour. Defaults: 365-day window, `base` USD, `sort` deepest, `universe` liquid, `limit` 10. Returns `{ base, from, to, mode, results[] }`; peak/trough dates are omitted and recovery fields are null when there is no drawdown or recovery in the window. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

Input parameters:

- `base` (string): Base currency to measure against (3-letter ISO 4217). Defaults to USD.
- `currency` (string): Currency to measure (3-letter ISO 4217), or a comma-separated list. OMIT to RANK the liquid set by drawdown.
- `from` (string): Window start YYYY-MM-DD (UTC). Defaults to 365 days before `to`.
- `limit` (number): Ranking: how many to return (default 10, max 50).
- `sort` (string): Ranking direction: deepest (largest decline first, default) or recovery (fastest recovery first).
- `to` (string): Window end YYYY-MM-DD (UTC). Defaults to today.
- `universe` (string): Ranking universe: liquid (default) or majors.

Output parameters:

- `base` (string)
- `from` (string)
- `mode` (string)
- `results` (array)
- `sort` (string)
- `to` (string)
- `universe` (string)

### `analyze_safe_haven` (~329 tokens)

Safe-haven analysis

Rank currencies by a 0–100 safe-haven score that combines low volatility, shallow drawdown, and 2008-crisis resilience. Use for "which currency holds up in a crisis" questions. Provide `currencies` to score specific codes, or omit to rank the liquid-fiat pool. Precious metals are not supported. Use `analyze_volatility` for pure dispersion and `analyze_drawdown` for peak-to-trough loss. Defaults: window from 2007-01-01 (or 20 years before `to`), `base` USD, `limit` 10. Returns `{ base, from, to, crisis, results[] }`. Returns an error when no rate data is available for the window. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

Input parameters:

- `base` (string): Base currency to measure against (3-letter ISO 4217). Defaults to USD.
- `currencies` (string): Comma-separated currencies to score, e.g. CHF,JPY. OMIT to rank the liquid-fiat safe-haven pool (precious metals are not supported).
- `from` (string): Window start YYYY-MM-DD (UTC). Defaults to 2007-01-01 (spans the 2008 crisis + COVID), or to 20 years before `to` when that is later.
- `limit` (number): How many to return (default 10, max 50).
- `to` (string): Window end YYYY-MM-DD (UTC). Defaults to today.

Output parameters:

- `base` (string)
- `crisis` (object)
- `from` (string)
- `results` (array)
- `to` (string)
- `universe` (string)

### `analyze_mean_reversion` (~281 tokens)

Mean-reversion analysis

Rank currencies by how strongly they revert to their historical mean, using a composite 0–100 score (crossing frequency + reversion half-life), plus current deviation and half-life in days. Use for questions like "does EUR snap back to its average". Provide `currencies` to score specific codes, or omit to rank the liquid set. Use `analyze_history` for raw change and `analyze_volatility` for dispersion. Defaults: roughly a 2-year window, `base` USD, `limit` 10. Returns `{ base, from, to, results[] }`; `score` and `halfLifeDays` are null when there is not enough reverting data. Requires a signed-in connection and the Growth plan or higher; each successful call bills 1 API request.

Input parameters:

- `base` (string): Base currency to measure against (3-letter ISO 4217). Defaults to USD.
- `currencies` (string): Comma-separated currencies to score, e.g. EUR,GBP. OMIT to rank the liquid set.
- `from` (string): Window start YYYY-MM-DD (UTC). Defaults to ~2 years before `to`.
- `limit` (number): How many to return (default 10, max 50).
- `to` (string): Window end YYYY-MM-DD (UTC). Defaults to today.

Output parameters:

- `base` (string)
- `from` (string)
- `results` (array)
- `to` (string)
- `universe` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/currencycore-currency-core-mcp/mcp#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 79

## Common questions

### What is the CurrencyCore MCP server?

CurrencyCore is an MCP server listed in the public MCP registry as io.github.CurrencyCore/currency-core-mcp. Live FX rates, conversion, IMF PPP, and historical currency analytics. This page covers its hosted endpoint (https://mcp.currency-core.com/mcp).

### Is the CurrencyCore MCP server safe to use?

CurrencyCore scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CurrencyCore MCP server expose?

CurrencyCore exposes 14 tools: list_countries, list_currencies, convert, get_rates, get_rates_by_base, and 9 more. Their descriptions and schemas cost roughly 4,042 tokens of context every time the server is loaded.

### Does the CurrencyCore MCP server require authentication?

No. We connected to CurrencyCore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CurrencyCore MCP server still maintained?

CurrencyCore is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the CurrencyCore MCP server?

VerifyMCP ran 13 checks on CurrencyCore, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.currency-core.com/mcp
- Repository: https://github.com/CurrencyCore/currency-core-mcp
- Website: https://currency-core.com/
- Changelog RSS feed: https://verifymcp.io/servers/currencycore-currency-core-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/currencycore-currency-core-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/currencycore-currency-core-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/currencycore-currency-core-mcp/mcp
