_ registry / mcp streamable-http

aiball

https://aiball.samagent.ai

Registry code: 5f45568e8a1cfc7c

api record

Football match outcome probabilities recorded before kick-off, and an open record of results.

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

endpoint
https://aiball.samagent.ai/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 aiball live?
Not measured yet: the hub has not completed a check of this server.
Is aiball free to use?
Not measured yet.
What tools does aiball have?
4 tools: list_matches, get_open_record, get_match_analysis, get_match_context.
Is aiball 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
unknown
uptime
—
latency
—

last good check

priced tools
0

of 4 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • list_matches unknown never probed

    Matches on one calendar day with their status: upcoming, pending (reading shown, not yet locked) or finished.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "tz": {
      "type": "string",
      "default": "Asia/Kuala_Lumpur",
      "description": "IANA time zone used to decide which calendar day a match falls on."
    },
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD. Defaults to today in tz."
    },
    "lang": {
      "enum": [
        "en",
        "ms"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of team and league names."
    },
    "league": {
      "type": "string",
      "description": "League name filter, optional."
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • get_open_record unknown never probed

    Hits out of matches for the public record, the pre-match favourite and random baselines on the same matches, results by confidence band, and snapshot coverage. Without week_start it covers the whole record; with it, that week only.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "tz": {
      "type": "string",
      "default": "Asia/Kuala_Lumpur",
      "description": "IANA time zone used to decide which calendar day a match falls on."
    },
    "lang": {
      "enum": [
        "en",
        "ms"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of team and league names."
    },
    "week_start": {
      "type": "string",
      "description": "YYYY-MM-DD, the Monday of the week. Optional."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • get_match_analysis unknown never probed

    Home / draw / away probabilities from each available model, the most likely outcome, the confidence, the pre-match favourite, when the reading was locked, and the result with a hit flag once the match has finished.

    mcp-tool

    {
  "type": "object",
  "required": [
    "match_id"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ms"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of team and league names."
    },
    "match_id": {
      "type": "string",
      "description": "Match id from list_matches."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • get_match_context unknown never probed

    Head-to-head summary, recent form, injuries and suspensions, and schedule density, limited to what is shown publicly on the site.

    mcp-tool

    {
  "type": "object",
  "required": [
    "match_id"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "ms"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of team and league names."
    },
    "match_id": {
      "type": "string",
      "description": "Match id from list_matches."
    }
  },
  "additionalProperties": false
}
    arguments 22 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 5f45568e8a1cfc7c.

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

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.