_ registry / mcp streamable-http · checked 1h ago

fx-reference-rates

https://fx-reference-rates.regnotes.workers.dev

Registry code: 7ffd9be2d39085db

api record

Paid tools use x402 v2 (USDC on Base). Call a tool, receive PaymentRequired in structuredContent, sign, retry with params._meta["x402/payment"]. ECB reference rates, informational only.

endpoint
https://fx-reference-rates.regnotes.workers.dev/mcp
protocol
streamable-http ·2025-06-18
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 fx-reference-rates live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is fx-reference-rates free to use?
No — it charges per call, from 0.001 USDC, quoted in its own 402 answers.
What tools does fx-reference-rates have?
4 tools: convert, rates_latest, rates_historical, rates_timeseries.
Is fx-reference-rates 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
100%

90 days 100%· all time 100%

latency
222ms

last good check

priced tools
4

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 4 tools
4 paid 4 of 4 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.

  • convert 0.001 USDC paid 1h ago

    Convert an amount using ECB reference rates (latest, or as of a past date). Costs $0.001 USDC on Base via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to",
        "amount"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "ISO 4217"
        },
        "date": {
          "type": "string",
          "description": "Optional YYYY-MM-DD"
        },
        "from": {
          "type": "string",
          "description": "ISO 4217"
        },
        "amount": {
          "type": "number",
          "description": "Number"
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • rates_latest 0.001 USDC paid 1h ago

    Most recent ECB reference rates expressed in the requested base currency. Costs $0.001 USDC on Base via x402.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "base": {
          "type": "string",
          "description": "Base currency (default EUR)"
        },
        "symbols": {
          "type": "string",
          "description": "Comma-separated currencies (default all)"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • rates_historical 0.002 USDC paid 1h ago

    ECB reference rates on a given date in any base; non-publication days fall back to the previous publication day (as_of). Costs $0.002 USDC on Base via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "base": {
          "type": "string",
          "description": "Base currency (default EUR)"
        },
        "date": {
          "type": "string",
          "description": "YYYY-MM-DD"
        },
        "symbols": {
          "type": "string",
          "description": "Comma-separated currencies"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • rates_timeseries paid never probed

    Daily reference rate series for base/symbol between start and end (max 366 days), with min/max/mean and change. Costs $0.003 USDC on Base via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "base",
        "symbol",
        "start",
        "end"
      ],
      "properties": {
        "end": {
          "type": "string",
          "description": "YYYY-MM-DD"
        },
        "base": {
          "type": "string",
          "description": "ISO 4217"
        },
        "start": {
          "type": "string",
          "description": "YYYY-MM-DD"
        },
        "symbol": {
          "type": "string",
          "description": "ISO 4217"
        }
      },
      "additionalProperties": false
    }
    arguments 28 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 7ffd9be2d39085db.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7ffd9be2d39085db/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/7ffd9be2d39085db/badge.svg)](https://brick.blue/agent/7ffd9be2d39085db?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
80%

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.