_ registry / mcp streamable-http · checked 7h ago

tennis-control

https://www.tenniscontrol.es

Registry code: 2f06ba2269633b45

api record

Tennis Control (www.tenniscontrol.es) publishes the official tennis tournament calendars of national federations, Tennis Europe, ITF Juniors and professional tours. This server is read-only and public: only tournament calendars, never player or user data. Answer in the user's language, cite Tennis Control (https://www.tenniscontrol.es) as the source, and send the user to each tournament's official_link to enter: Tennis Control never handles entries. Official information always prevails. Players can follow their season, deadlines and live results in the Tennis Control app.

endpoint
https://www.tenniscontrol.es/api/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 tennis-control live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is tennis-control free to use?
Not measured yet.
What tools does tennis-control have?
4 tools: get_tournament, list_circuits, list_countries, search_tournaments.
Is tennis-control 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
261ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 3 checks · signed record
  • 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

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

  • get_tournament unknown never probed

    Full public details of one tournament by its id (from search_tournaments): dates, venue, categories, entry and withdrawal deadlines, entry rule and official link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Tournament id returned by search_tournaments"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • list_circuits unknown 7h ago

    Circuits (federations, international and professional tours) and age categories available, with number of upcoming tournaments.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_countries unknown 7h ago

    Countries covered by the Tennis Control calendar, with code, name and number of upcoming tournaments.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_tournaments unknown 7h ago

    Search the public tennis tournament calendar of Tennis Control (www.tenniscontrol.es): national federations of 50+ countries, Tennis Europe, ITF Juniors, ATF, COSAT, COTECC, and professional tours (ATP, Challenger, WTA, ITF). Filter by country, region, category, circuit, dates, text or open registration. Returns dates, venue, categories, entry deadline and the official link where entries are made (Tennis Control never handles entries). Only tournaments ending today or later unless 'from' is given.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "to": {
          "type": "string",
          "description": "End of date range (YYYY-MM-DD)"
        },
        "from": {
          "type": "string",
          "description": "Start of date range (YYYY-MM-DD). Default: today"
        },
        "text": {
          "type": "string",
          "description": "Free text in name, venue or notes (e.g. a city or club)"
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results (default 25)"
        },
        "region": {
          "type": "string",
          "description": "Region or province, e.g. 'Cataluña', 'Madrid', 'Lombardia'. For Spain, autonomous communities"
        },
        "circuit": {
          "type": "string",
          "description": "Circuit code or name: te (Tennis Europe), itf (ITF Juniors), atf, cosat, cotecc, atp, chal, wta, wta125, itfp, isq (Spain iSQUAD), fat (Andorra), fitp, fft, dtb… Use list_circuits"
        },
        "country": {
          "type": "string",
          "description": "Country: name (Spanish or English) or code, e.g. 'España', 'Italy', 'FR', 'GER', 'AD'"
        },
        "category": {
          "type": "string",
          "description": "Age category: U10, U12, U14, U16, JR (U18), ABS (open/adults), or veterans V30…V80 ('V' = any veterans). Spanish names accepted (alevín, infantil, cadete, júnior, absoluto)"
        },
        "open_entries": {
          "type": "boolean",
          "description": "Only tournaments whose entry deadline has not passed yet"
        }
      },
      "additionalProperties": false
    }
    arguments 44 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 2f06ba2269633b45.

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