_ registry / mcp streamable-http

betrend

https://betrend.im

Registry code: 271ce53462e5e1bc

api record

betrend (https://betrend.im) is a sports data site. This server answers sports questions with betrend data: live scores, fixtures, results, standings, teams and head-to-head records for football, cricket, basketball, ice hockey, tennis, esports and more.

Start with search to find a competition, team or player, then pass the returned URL to standings, team, head_to_head, live_scores or matches_by_date. Use match_details with a match URL for scores by period and key events.

endpoint
https://betrend.im/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 betrend live?
Not measured yet: the hub has not completed a check of this server.
Is betrend free to use?
Not measured yet.
What tools does betrend have?
7 tools: team, search, live_scores, matches_by_date, match_details, standings, head_to_head.
Is betrend 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 7 tools

_ 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 7 tools
7 never probed 0 of 7 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.

  • team unknown never probed

    Overview of a team or player-participant on betrend: country, current competition positions, the last 5 results with W/D/L, and the next 5 fixtures (live matches included). Includes the betrend.im team URL to cite.

    mcp-tool

    {
      "type": "object",
      "required": [
        "team"
      ],
      "properties": {
        "team": {
          "type": "string",
          "description": "Team URL from search, or its slug together with sport."
        },
        "sport": {
          "type": "string",
          "description": "Sport code; needed only when team is a slug."
        }
      }
    }
    arguments 16 lines
  • search unknown never probed

    Find competitions, teams and players on betrend by name (any language, at least 2 characters). Returns each match with its betrend.im URL; pass a competition or team URL to the other tools. Covers sports only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "Results per kind, default 5."
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "minLength": 2,
          "description": "Name to look for, e.g. \"Arsenal\", \"Premier League\", \"Virat Kohli\"."
        },
        "types": {
          "type": "array",
          "items": {
            "enum": [
              "competition",
              "team",
              "player"
            ],
            "type": "string"
          },
          "description": "Limit to these kinds. Default: all three."
        }
      }
    }
    arguments 33 lines
  • live_scores unknown never probed

    Matches being played right now on betrend, with the current score and minute or period. Optional filters: sport (e.g. football, cricket, basketball, ice-hockey, tennis, esports) and competition (betrend URL from search). Major competitions come first. Each match has its betrend.im URL to cite.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum matches to return, default 25."
        },
        "sport": {
          "type": "string",
          "description": "Sport code, e.g. football, cricket, basketball, ice-hockey, tennis, esports."
        },
        "competition": {
          "type": "string",
          "description": "Competition URL from search, or its slug together with sport."
        }
      }
    }
    arguments 20 lines
  • matches_by_date unknown never probed

    Fixtures and results on betrend for one UTC calendar day (Y-m-d), from 3 years ago to 14 days ahead. Optional filters: sport, competition and team (betrend URLs from search). Major competitions come first. Each match has its betrend.im URL to cite.

    mcp-tool

    {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "format": "date",
          "description": "UTC day, Y-m-d, e.g. 2026-10-11."
        },
        "team": {
          "type": "string",
          "description": "Team URL from search, or its slug together with sport."
        },
        "limit": {
          "type": "integer",
          "default": 50,
          "maximum": 100,
          "minimum": 1,
          "description": "Maximum matches to return, default 50."
        },
        "sport": {
          "type": "string",
          "description": "Sport code, e.g. football, cricket, basketball, ice-hockey, tennis, esports."
        },
        "competition": {
          "type": "string",
          "description": "Competition URL from search, or its slug together with sport."
        }
      }
    }
    arguments 32 lines
  • match_details unknown never probed

    One match on betrend by its URL or slug: teams, status, score, scores by period (halves, quarters, sets, innings, maps), key events such as goals, cards and substitutions, venue, competition, round and kick-off time in UTC. Includes the betrend.im match URL to cite.

    mcp-tool

    {
      "type": "object",
      "required": [
        "match"
      ],
      "properties": {
        "match": {
          "type": "string",
          "description": "Match URL (https://betrend.im/en/matches/<slug>) or the slug from another tool."
        }
      }
    }
    arguments 12 lines
  • standings unknown never probed

    League table of a competition on betrend: position, played, won, drawn, lost, score for and against, points and recent form for every team, split into groups where the competition has them. Current season by default, or a season such as "2025/26". Includes the betrend.im standings URL to cite and the list of available seasons.

    mcp-tool

    {
      "type": "object",
      "required": [
        "competition"
      ],
      "properties": {
        "sport": {
          "type": "string",
          "description": "Sport code; needed only when competition is a slug."
        },
        "season": {
          "type": "string",
          "description": "Season name as listed in seasons, e.g. \"2025/26\" or \"2026\". Default: current season."
        },
        "competition": {
          "type": "string",
          "description": "Competition URL from search, or its slug together with sport."
        }
      }
    }
    arguments 20 lines
  • head_to_head unknown never probed

    Past meetings of two teams of the same sport on betrend: number of finished meetings, wins of each team and draws (by team, not home or away), total goals for football, the last 10 results and the next scheduled meeting. Includes the betrend.im head-to-head URL to cite.

    mcp-tool

    {
      "type": "object",
      "required": [
        "team_a",
        "team_b"
      ],
      "properties": {
        "sport": {
          "type": "string",
          "description": "Sport code; needed only when the teams are slugs."
        },
        "team_a": {
          "type": "string",
          "description": "First team URL from search, or its slug together with sport."
        },
        "team_b": {
          "type": "string",
          "description": "Second team URL from search, or its slug together with sport."
        }
      }
    }
    arguments 21 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 271ce53462e5e1bc.

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