_ registry / mcp streamable-http · checked 53m ago

Exchange Rate API

https://exchange-rate.nimbus-api.com

Registry code: 4867858f60700849

api record

Real-time and historical exchange rates for 160 fiat, crypto, and precious metal currencies. Hourly updates from ECB, FloatRates, and CoinGecko. Free base switching, time-series, batch conversion, and historical data back to 1999.

from a public catalogue that lists it, not from the operator

endpoint
https://exchange-rate.nimbus-api.com/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Exchange Rate API live?
Yes — it answered the hub's last check (checked 53m ago). It answered 99% of checks over the last 30 days.
Is Exchange Rate API free to use?
Not measured yet.
What tools does Exchange Rate API have?
6 tools: get_latest_rates, list_currencies, get_historical_rates, batch_convert, get_timeseries, convert_currency.
Is Exchange Rate API safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.3%· all time 99.3%

latency
980ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 272 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get latest exchange rates
  • convert an amount between currencies
  • get historical exchange rates for a date
  • get a daily rate time series
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_latest_rates reads unknown never probed

    Get the latest exchange rates for all or specific currencies. Supports any base currency (e.g. USD, EUR, BTC) and optional symbol filtering. Rates updated hourly from ECB, FloatRates, and CoinGecko. Returns rates for 160 currencies including fiat, crypto, and precious metals.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "base": {
          "type": "string",
          "default": "EUR",
          "example": "USD",
          "description": "Base currency (ISO 4217)"
        },
        "symbols": {
          "type": "string",
          "example": "EUR,GBP,BTC",
          "description": "Comma-separated target currencies"
        }
      }
    }
    arguments 16 lines
  • list_currencies reads unknown never probed

    List all 160 supported currencies with metadata: code, name, symbol, flag emoji, decimal places, and type (fiat, crypto, or metal). No API key required.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_historical_rates reads unknown never probed

    Get exchange rates for a specific historical date (format: YYYY-MM-DD). Data available back to 1999 for fiat currencies. Supports base currency switching and symbol filtering.

    mcp-tool

    {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "base": {
          "type": "string",
          "default": "EUR",
          "example": "USD",
          "description": "Base currency"
        },
        "date": {
          "type": "string",
          "example": "2024-01-15",
          "description": "Date (YYYY-MM-DD)"
        },
        "symbols": {
          "type": "string",
          "example": "EUR,GBP",
          "description": "Comma-separated target currencies"
        }
      }
    }
    arguments 24 lines
  • batch_convert reads unknown never probed

    Convert multiple currency pairs in a single request. Submit up to 100 conversion pairs (from, to, amount) and get all results at once. More efficient than multiple convert calls.

    mcp-tool

    {
      "type": "object",
      "required": [
        "conversions"
      ],
      "properties": {
        "conversions": {
          "type": "array",
          "description": "Array of currency conversion requests, each with from, to, and amount fields (1-100 items)"
        }
      }
    }
    arguments 12 lines
  • get_timeseries reads unknown never probed

    Get daily exchange rates over a date range (start_date to end_date, YYYY-MM-DD, max 365 days). Returns an array of daily rate objects. Useful for charts, trend analysis, and backtesting.

    mcp-tool

    {
      "type": "object",
      "required": [
        "start",
        "end"
      ],
      "properties": {
        "end": {
          "type": "string",
          "example": "2024-01-31",
          "description": "End date"
        },
        "base": {
          "type": "string",
          "default": "EUR",
          "example": "USD",
          "description": "Base currency"
        },
        "start": {
          "type": "string",
          "example": "2024-01-01",
          "description": "Start date"
        },
        "symbols": {
          "type": "string",
          "example": "EUR,GBP",
          "description": "Comma-separated currencies"
        }
      }
    }
    arguments 30 lines
  • convert_currency reads unknown never probed

    Convert a specific amount from one currency to another using the latest or historical exchange rates. Returns the converted amount, rate used, and currency metadata. Supports all 160 currencies.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to",
        "amount"
      ],
      "properties": {
        "to": {
          "type": "string",
          "example": "EUR",
          "description": "Target currency"
        },
        "date": {
          "type": "string",
          "description": "Historical date (optional)"
        },
        "from": {
          "type": "string",
          "example": "USD",
          "description": "Source currency"
        },
        "amount": {
          "type": "number",
          "example": 100,
          "description": "Amount to convert"
        }
      }
    }
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4867858f60700849.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4867858f60700849/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4867858f60700849/badge.svg)](https://brick.blue/agent/4867858f60700849?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.