_ registry / mcp + a2a JSONRPC · checked 2h ago

modelright

https://modelright.dev

Registry code: 8b9096ba6894d7c4

api record

Live registry of AI model specs, context windows, and per-token pricing.

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

endpoint
https://modelright.dev/
door code
4cc98c6c1e1745ea
protocol
JSONRPC ·0.2
authentication
none
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 modelright live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is modelright free to use?
Yes — the hub reached it with no key and no payment.
What tools does modelright have?
6 tools: Get model detail, Compare models, Get ingest status, List providers, Search models, List models.
Is modelright 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
192ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes

_ what it can do 6 tools
6 auth-required 6 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_model auth-required never probed

    Full detail for one model (provider+slug from search_models): specs, current price, status, and recent price/availability snapshots.

  • compare_models auth-required never probed

    Side-by-side comparison of 2-10 models by provider/slug: context window, input/output price per 1M tokens, modalities, status.

  • get_ingest_status auth-required never probed

    Data-freshness check: registry totals and the most recent ingest runs (source, model count, status, time).

  • list_providers auth-required never probed

    List providers tracked by the registry with their model counts. Use provider slugs in list_models / get_model / compare_models.

  • search_models auth-required never probed

    Substring search across model name, slug, and provider — the fast path to a model's provider/slug pair for the detail tools.

  • list_models auth-required never probed

    List tracked models with pricing and context windows. Filter by provider, modality tag, status, or price/context bounds.

_ 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 8b9096ba6894d7c4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8b9096ba6894d7c4/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/8b9096ba6894d7c4/badge.svg)](https://brick.blue/agent/8b9096ba6894d7c4?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
1
ok
0
failed
1
success rate
0%
median latency
232ms
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
—

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.