_ registry / mcp + a2a JSONRPC · checked 7m ago

rarasnet-http

https://raras.org

Registry code: 8e90125f97b03aa3

api record

RarasNet MCP — Brazilian Rare Disease Knowledge Graph. Each rare disease is an addressable "Disease Twin" (resource `disease://{orphaCode}`). All outputs in PT-BR by default. Include ORPHA/MONDO/HPO codes. Every fact traces to an authoritative source (use get_evidence). Never diagnose — suggest medical consultation.

endpoint
https://raras.org/api/a2a
door code
b48c7a8c43cb56c9
protocol
JSONRPC ·0.3
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 rarasnet-http live?
Yes — it answered the hub's last check (checked 7m ago). It answered 100% of checks over the last 30 days.
Is rarasnet-http free to use?
Yes — the hub reached it with no key and no payment.
What tools does rarasnet-http have?
2 tools: Consulta de doença rara, Diferencial por sintomas.
Is rarasnet-http 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
99.8%

90 days 99.5%· all time 99.6%

latency
170ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1050 checks · signed record
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • down → live
  • down → live
  • degraded → live
_ what it is for
topic
health & science health & medical
used for
  • search rare diseases
  • find diseases matching phenotypes
  • find clinical trials for a rare disease
  • find reference treatment centers in brazil
  • search biomedical literature for a disease
takes → gives
text → data, text
_ 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 closed 2 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.

  • disease_lookup closed never probed

    Dado o nome de uma doença rara, retorna um resumo fundamentado (IDs ORPHA/MONDO, genes, cobertura SUS) com links para as fontes.

    rare-diseaseorphanethposuspt-br

  • differential_by_symptoms closed never probed

    Dado um conjunto de sintomas, sugere doenças raras candidatas (informativo, nunca diagnóstico).

    differential-diagnosishpophenotype

_ try it over a2a 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 8e90125f97b03aa3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8e90125f97b03aa3/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/8e90125f97b03aa3/badge.svg)](https://brick.blue/agent/8e90125f97b03aa3?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 knowoff the mcp door
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.