bcv-today
Registry code: 876f7288d3b92ca5
BCV Today: official exchange rates published by Banco Central de Venezuela (BCV). Rates are bolivars (VES) per one unit of USD, EUR, CNY, TRY or RUB. effective_date is the official BCV validity date ('fecha valor'); updated_at is the UTC capture time. BCV does not publish on weekends and holidays: the last published rate stays in effect, so effective_date may be earlier than the requested date. Data is free, public and read-only. Unofficial project, not affiliated with the bank. Docs: https://bcv.today/llms.txt
- endpoint
- https://mcp.bcv.today/mcp
- door code
- 1a240ec882f0d247
- 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 bcv-today live?
- Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
- Is bcv-today free to use?
- Not measured yet.
- What tools does bcv-today have?
- 5 tools: get_status, get_latest_rates, convert, get_rate_by_date, get_history.
- Is bcv-today 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.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
- unknown → live
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.
through this hub
successful
what callers paid
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_status unknown never probed
Freshness of the published BCV data: status, last capture time, effective date, age in hours and supported currencies.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_latest_rates unknown never probed
Official BCV exchange rates currently in effect for USD, EUR, CNY, TRY and RUB, in bolivars (VES) per unit, with effective date and capture time.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesconvert unknown never probed
Convert an amount between VES, USD, EUR, CNY, TRY and RUB using the official BCV rate currently in effect, or the rate in effect on a given date (YYYY-MM-DD).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "amount", "from", "to" ], "properties": { "to": { "enum": [ "VES", "USD", "EUR", "CNY", "TRY", "RUB" ], "type": "string", "description": "Target currency code." }, "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Use the rate in effect on this day (YYYY-MM-DD). Omit for the latest rate." }, "from": { "enum": [ "VES", "USD", "EUR", "CNY", "TRY", "RUB" ], "type": "string", "description": "Source currency code." }, "amount": { "type": "number", "maximum": 1000000000000000, "minimum": 0, "description": "Amount to convert, e.g. 100." } } }arguments 46 linesget_rate_by_date unknown never probed
Official BCV rate(s) in effect on a calendar day (YYYY-MM-DD, from 2021-08-02). Weekends and holidays carry forward the last published rate; the response explains it. Optionally restrict to one currency.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "date" ], "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Calendar day, YYYY-MM-DD (e.g. 2026-01-02)." }, "currency": { "enum": [ "USD", "EUR", "CNY", "TRY", "RUB" ], "type": "string", "description": "Only return this currency. Omit for all available." } } }arguments 25 linesget_history unknown never probed
Daily official BCV rate series for one currency, either the last N calendar days (days, default 30, max 1830) or a from/to date range, with min, max and percentage change.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "currency" ], "properties": { "to": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Range end, YYYY-MM-DD (inclusive). Defaults to the latest date." }, "days": { "type": "integer", "maximum": 1830, "minimum": 1, "description": "Last N calendar days ending on the latest published date (default 30). Ignored when from/to is given." }, "from": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Range start, YYYY-MM-DD (inclusive)." }, "currency": { "enum": [ "USD", "EUR", "CNY", "TRY", "RUB" ], "type": "string", "description": "Currency to chart against the bolivar." } } }arguments 36 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id876f7288d3b92ca5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/876f7288d3b92ca5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/876f7288d3b92ca5?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 342ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- bcv.today BCV Today Data Agent