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

ComparaDolar

https://comparadolar.pe

Registry code: d84e9181e759ab08

api record

Live USD/PEN rate ranking of Peru's SBS-supervised online exchange houses, from comparadolar.pe

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

endpoint
https://comparadolar.pe/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 ComparaDolar live?
Yes — it answered the hub's last check (checked 55m ago). It answered 99% of checks over the last 30 days.
Is ComparaDolar free to use?
Not measured yet.
What tools does ComparaDolar have?
2 tools: referencias_dolar, mejor_tasa.
Is ComparaDolar 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.7%

90 days 99.3%· all time 99.3%

latency
331ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 286 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
finance & markets forex & rates
used for
  • find best usd pen exchange rate in peru
  • get official and parallel dollar rates
takes → gives
data → data
tools
2 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 2 tools
2 never probed 0 of 2 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.

  • referencias_dolar reads unknown never probed

    Tipos de cambio de REFERENCIA del día en Perú: el oficial SBS/SUNAT, el dólar paralelo/informal y el USDT P2P (cripto). NO son casas de cambio — sirven para contextualizar y comparar contra el ranking de mejor_tasa.

    mcp-tool

    {
  "type": "object",
  "title": "referencias_dolarArguments",
  "properties": {}
}
    arguments 5 lines
  • mejor_tasa reads unknown never probed

    Ranking EN VIVO de las casas de cambio virtuales del Perú (solo supervisadas por la SBS) para comprar o vender dólares, desde comparadolar.pe. Úsala cuando pregunten dónde cambiar dólares, cuál es la mejor tasa hoy, o cuánto recibirían por un monto. Devuelve el top de casas con su precio y, si se indica monto, cuánto recibe el usuario en cada una y el ahorro entre la mejor y la peor.

    mcp-tool

    {
  "type": "object",
  "title": "mejor_tasaArguments",
  "properties": {
    "top": {
      "type": "integer",
      "title": "Top",
      "default": 5,
      "description": "Cuántas casas devolver (1-10)"
    },
    "monto": {
      "anyOf": [
        {
          "type": "number"
        },
        {
          "type": "null"
        }
      ],
      "title": "Monto",
      "default": null,
      "description": "Monto a cambiar (en SOLES si operacion=comprar, en DÓLARES si vender). Opcional"
    },
    "operacion": {
      "type": "string",
      "title": "Operacion",
      "default": "vender",
      "description": "'comprar' = pagar soles y recibir USD; 'vender' = entregar USD y recibir soles"
    }
  }
}
    arguments 31 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 d84e9181e759ab08.

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

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.