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

Bzzoiro Sports Data

https://sports.bzzoiro.com

Registry code: c90dd97ff530a6d7

api record

Real-time football data for Claude. Search players, managers, and matches with live stats including xG, ratings, key passes, and performance metrics. Covers La Liga, Champions League, Premier League and more. Built on bzzoiro.com sports analytics platform.

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

endpoint
https://sports.bzzoiro.com/api/
door code
302d859a79d78d8d
protocol
JSONRPC ·1.0
authentication
token
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 Bzzoiro Sports Data live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Bzzoiro Sports Data free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Bzzoiro Sports Data have?
5 tools: Football Data, Live Scores, Spatial Data, ML Predictions, Odds Comparison.
Is Bzzoiro Sports Data 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.5%

90 days 99.6%· all time 100%

latency
124ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 931 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
_ what it is for
topic
games & entertainment sports
used for
  • get live football scores
  • get player and match stats
  • compare betting odds
  • get match predictions
  • get league standings
takes → gives
text → data
_ 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 5 tools
5 auth-required 5 of 5 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.

  • football-data auth-required never probed

    Retrieve leagues, teams, matches, and player stats for 34 leagues and 21,000+ players.

    footballsoccerleaguesteamsplayers

  • live-scores auth-required never probed

    Real-time football match scores with incidents, statistics, and live events.

    livescoresfootballrealtime

  • spatial-data auth-required never probed

    Shot maps with per-shot xG, average positions, momentum timelines, and goal sequences for matches.

    xgshotmapmomentumpositions

  • predictions auth-required never probed

    CatBoost machine-learning predictions for 8 football betting markets with calibrated probabilities and edge detection.

    predictionsmlbettingmarkets

  • odds auth-required never probed

    Multi-bookmaker odds comparison (~14 books) with previous price + is_max_quote per row, plus Polymarket prediction market prices.

    oddsbookmakerspolymarketbetting

_ 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 c90dd97ff530a6d7.

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