_ registry / mcp streamable-http · checked 45m ago

jobs-in-sports-tech

https://jobsinsportstech.com

Registry code: a72fef1223b112dc

api record

Live listings of open roles at sports technology companies, refreshed daily from employers' own job feeds by jobsinsportstech.com.

endpoint
https://jobsinsportstech.com/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 jobs-in-sports-tech live?
Yes — it answered the hub's last check (checked 45m ago). It answered 100% of checks over the last 30 days.
Is jobs-in-sports-tech free to use?
Yes — the hub reached it with no key and no payment.
What tools does jobs-in-sports-tech have?
3 tools: subscribe_to_job_alerts, list_hiring_companies, search_jobs.
Is jobs-in-sports-tech 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
600ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 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 3 tools
2 open 1 never probed 2 of 3 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_hiring_companies open 45m ago

    List sports technology companies ranked by how many open roles they have, with how many roles each added in the last 30 days. Optionally filter by region or job function.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum companies to return (1–50)."
        },
        "region": {
          "enum": [
            "UK",
            "Europe",
            "North America",
            "LATAM",
            "APAC",
            "Middle East & Africa",
            "Remote",
            "Global/Other"
          ],
          "type": "string",
          "description": "Only count roles in this region."
        },
        "function": {
          "enum": [
            "Engineering",
            "Data & Analytics",
            "Product",
            "Design",
            "Commercial",
            "Marketing",
            "Operations",
            "Trading & Risk",
            "People & Finance",
            "Other"
          ],
          "type": "string",
          "description": "Only count roles in this job function."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • search_jobs open 45m ago

    Search open roles at sports technology companies (sports data, betting tech, wearables, fan engagement, ticketing, performance analytics, fitness tech, clubs and leagues). Listings are refreshed daily from employers' own job feeds. Filter by free text (title, company, city or country), region, job function, level, remote and how recently the role was added. Returns each role with company, location, level, date and a link to the listing.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "level": {
          "enum": [
            "internship_or_graduate",
            "junior",
            "mid",
            "senior",
            "leadership"
          ],
          "type": "string",
          "description": "Seniority. \"internship_or_graduate\" covers internships, graduate schemes and entry-level roles."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1,
          "description": "Maximum roles to return (1–25)."
        },
        "query": {
          "type": "string",
          "description": "Free-text words to match in title, company, city or country, e.g. \"data analyst\", \"Genius Sports\", \"London\"."
        },
        "region": {
          "enum": [
            "UK",
            "Europe",
            "North America",
            "LATAM",
            "APAC",
            "Middle East & Africa",
            "Remote",
            "Global/Other"
          ],
          "type": "string",
          "description": "Region the role is based in. \"Remote\" returns remote roles anywhere."
        },
        "remote": {
          "type": "boolean",
          "description": "true to return only remote roles."
        },
        "company": {
          "type": "string",
          "description": "Exact or partial company name."
        },
        "function": {
          "enum": [
            "Engineering",
            "Data & Analytics",
            "Product",
            "Design",
            "Commercial",
            "Marketing",
            "Operations",
            "Trading & Risk",
            "People & Finance",
            "Other"
          ],
          "type": "string",
          "description": "Job function."
        },
        "added_within_days": {
          "type": "integer",
          "maximum": 90,
          "minimum": 1,
          "description": "Only roles first seen on the board within this many days."
        }
      },
      "additionalProperties": false
    }
    arguments 72 lines
  • subscribe_to_job_alerts unknown never probed

    Sign an email address up for Jobs in Sports Tech job alert emails, optionally with preferred regions and job functions. Use only with the user's own email address, given by the user for this purpose. The address is stored with the stated preferences only; every email includes an unsubscribe link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "The user's own email address."
        },
        "regions": {
          "type": "array",
          "items": {
            "enum": [
              "UK",
              "Europe",
              "North America",
              "LATAM",
              "APAC",
              "Middle East & Africa",
              "Remote",
              "Global/Other"
            ],
            "type": "string"
          },
          "maxItems": 8,
          "description": "Preferred regions (optional)."
        },
        "functions": {
          "type": "array",
          "items": {
            "enum": [
              "Engineering",
              "Data & Analytics",
              "Product",
              "Design",
              "Commercial",
              "Marketing",
              "Operations",
              "Trading & Risk",
              "People & Finance",
              "Other"
            ],
            "type": "string"
          },
          "maxItems": 10,
          "description": "Preferred job functions (optional)."
        }
      },
      "additionalProperties": false
    }
    arguments 51 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 a72fef1223b112dc.

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

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.