ssi-scoreboard

endpoint

https://scoreboard.urdr.dev/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 ssi-scoreboard live?

Yes — it answered the hub's last check (checked 14m ago). It answered 99% of checks over the last 30 days.

Is ssi-scoreboard 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 ssi-scoreboard have?

7 tools: get_shooter_dashboard, get_stage_times, compare_competitors, get_match, find_shooter, get_popular_matches, search_events.

Is ssi-scoreboard 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.

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_shooter_dashboard reads auth-required 5h ago

  Fetch a shooter's cross-competition profile and career statistics. Returns: profile (name, club, division), match history (up to 50 recent matches with per-match stats), aggregate stats (overall match %, average hit factor, A-zone %, consistency CV, HF trend slope), and achievement progress (tiered milestones). Use this to answer questions about a shooter's performance across multiple matches, their consistency over time, or how their accuracy has been trending. The `shooter_id` is the globally stable SSI ShooterNode ID — obtain it from `get_match`'s `competitors[n].shooterId` field (an integer, distinct from the per-match `competitors[n].id`). Returns 404 if the shooter has not been seen in any cached match on this server. Each match in `matches[]` includes `ct` and `matchId` so you can call `get_match` or `compare_competitors` to drill into a specific competition.

  mcp-tool

  123456789101112131415

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "shooter_id"
    ],
    "properties": {
      "shooter_id": {
        "type": "integer",
        "description": "Globally stable SSI shooter ID — from get_match competitors[n].shooterId (not the per-match competitor id)",
        "exclusiveMinimum": 0
      }
    },
    "additionalProperties": false
  }

  arguments 15 lines copy
• get_stage_times reads auth-required 8h ago

  Export raw stage times for a list of competitors at a match — built for video editors who want to auto-cut a long match recording into per-stage clips. Returns one object per competitor with a stages[] array; each entry has stage_number, stage_name, time_seconds (raw stage time), and scorecard_updated_at (ISO timestamp of when the run was recorded). Stages within each competitor are sorted by stage_number. Competitors are returned in the order of `competitor_ids`. competitor_ids are numeric IDs from get_match — resolve names with get_match first.

  mcp-tool

  123456789101112131415161718192021222324252627282930

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ct",
      "id",
      "competitor_ids"
    ],
    "properties": {
      "ct": {
        "type": "string",
        "description": "content_type value from search_events / get_match"
      },
      "id": {
        "type": "string",
        "description": "match id value from search_events / get_match"
      },
      "competitor_ids": {
        "type": "array",
        "items": {
          "type": "integer",
          "exclusiveMinimum": 0
        },
        "maxItems": 12,
        "minItems": 1,
        "description": "Numeric competitor IDs from get_match. Up to 12."
      }
    },
    "additionalProperties": false
  }

  arguments 30 lines copy
• compare_competitors reads auth-required 8h ago

  Run a deep stage-by-stage comparison for 1–12 competitors in a match. Returns scores, hit factors, penalties, efficiency %, consistency, time-vs-accuracy breakdown, what-if rank simulations, and performance fingerprints. Pass a single competitor ID to analyse one shooter in isolation. Pass multiple IDs to compare them head-to-head across every stage. `competitor_ids` are numeric IDs from get_match's competitor list — always resolve names to IDs via get_match first. IMPORTANT — ranking across competitors: NEVER rank by raw points. Points are not comparable across divisions (Production vs Classic Minor vs Standard Minor etc.) or across stages (each stage has different max_points). Use `overall_rank` (rank across all competitors regardless of division) and the average of per-stage `overall_percent` to rank cross-division. Use `div_rank` for within-division ranking. Use `penaltyStats[id].matchPctActual` for group-relative average match %. Results are suitable for natural-language coaching feedback, identifying where points were lost, and ranking analysis.

  mcp-tool

  123456789101112131415161718192021222324252627282930

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ct",
      "id",
      "competitor_ids"
    ],
    "properties": {
      "ct": {
        "type": "string",
        "description": "content_type value from the search_events result for this match"
      },
      "id": {
        "type": "string",
        "description": "id value from the search_events result for this match"
      },
      "competitor_ids": {
        "type": "array",
        "items": {
          "type": "integer",
          "exclusiveMinimum": 0
        },
        "maxItems": 12,
        "minItems": 1,
        "description": "Numeric competitor IDs from get_match. Up to 12. Resolve names to IDs with get_match before calling this."
      }
    },
    "additionalProperties": false
  }

  arguments 30 lines copy
• get_match reads auth-required 8h ago

  Fetch full details for a specific IPSC match. Returns the complete competitor list — each entry has a numeric `id`, `name`, `club`, and `division`. Also returns a `squads` list where each squad has a `name` (e.g. 'Squad 3') and a `competitorIds` array of every competitor in that squad. Use this to resolve any user reference to a competitor ID before calling compare_competitors: match by `name` for named individuals, filter by `club` for club members, or use `squads[n].competitorIds` for an entire squad. Always call this before compare_competitors. `ct` and `id` come from a search_events result (the `content_type` and `id` fields of the event). Each stage in `stages[]` includes `procedure` (free-text stage instructions), `firearm_condition` (loading requirements such as 'Unloaded'), `course_display` ('Short'/'Medium'/'Long'), `min_rounds`, `paper_targets`, and `steel_targets`. When `scoring_completed` is 0 (pre-match), use these fields for preparation analysis: compute the round-robin stage rotation for a squad, parse constraint signals from text, and summarise the course breakdown.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ct",
      "id"
    ],
    "properties": {
      "ct": {
        "type": "string",
        "description": "content_type value from a search_events result (typically '22' for IPSC matches)"
      },
      "id": {
        "type": "string",
        "description": "id value from a search_events result"
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• find_shooter reads auth-required 14m ago

  Search for shooter profiles by name. Returns a list of matching shooters with their shooter_id — pass that ID to get_shooter_dashboard to load their full career history. Only shooters who have appeared in at least one cached match on this server are searchable. Pass an empty query to browse the most recently active shooters. Use this when you know a shooter's name but not their shooter_id, as an alternative to browsing get_match competitor lists.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 20,
        "maximum": 100,
        "minimum": 1,
        "description": "Maximum number of results to return. Defaults to 20."
      },
      "query": {
        "type": "string",
        "default": "",
        "description": "Name to search for (case-insensitive substring match). Empty string returns recently seen shooters."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• get_popular_matches reads auth-required 14m ago

  List recently-viewed IPSC matches from the cache. Call this first whenever the user hasn't specified a match — it surfaces currently-active or recently-popular events so you can ask which one they mean, or proceed with the most relevant one. If the user asks a vague question like 'how did I do?' or 'what matches are on?', start here. Returns [] when the cache is cold (no recent visitors); fall back to search_events in that case.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• search_events reads auth-required 14m ago

  Search for IPSC competitions by name, country, date range, or level. Use this to find a specific match the user has named, or to browse upcoming/recent events. Each result contains `id` and `content_type` fields — pass both to get_match to load full details. When searching by name (query param), past events are included automatically — no date filter needed. When browsing without a query, only events within ~3 months of today are returned by default; pass explicit starts_after/starts_before to widen the window. Browse date ranges wider than 70 days are truncated (anchored at starts_after) — page with multiple narrower requests instead of one wide range. `min_level` defaults to l2plus which hides small club matches; pass 'all' only if the user explicitly wants club-level events.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "query": {
        "type": "string",
        "description": "Free-text search by event name or venue"
      },
      "country": {
        "type": "string",
        "maxLength": 3,
        "minLength": 3,
        "description": "ISO 3166-1 alpha-3 country code, e.g. SWE, NOR, FIN"
      },
      "min_level": {
        "enum": [
          "all",
          "l2plus",
          "l3plus",
          "l4plus"
        ],
        "type": "string",
        "description": "Minimum competition level. Defaults to l2plus (Regional and above). Use 'all' to include Level I club matches."
      },
      "starts_after": {
        "type": "string",
        "description": "Only return events starting on or after this date. ISO format: YYYY-MM-DD"
      },
      "starts_before": {
        "type": "string",
        "description": "Only return events starting on or before this date. ISO format: YYYY-MM-DD"
      }
    },
    "additionalProperties": false
  }

  arguments 35 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

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.