Skip to content

net.tipmaster/consensus

by tipmaster.net · remote · no sign-in to list tools · v1.1.0 · published by net.tipmaster

Friday expert picks on 25 football matches from players with records since 1997. Read-only, free.

Read only
CompareRegistry entry

4 tools: 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http consensus https://tipmaster.net/api/agent/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Only reads 4Claude Code: allow
  • get_consensusFull prediction record per match: the crowd’s home/draw/away shares (live while the round is open) and the expert cohort (expert.outcome, from the Friday 18:00 Europe/Berlin deadli…No findings

    Why it is in this group

    • The name "get_consensus" says "get": a word for reading.
    Description, as the server wrote it
    Full prediction record per match: the crowd’s home/draw/away shares (live while the round is open) and the expert cohort (expert.outcome, from the Friday 18:00 Europe/Berlin deadline; expert.criteria says how the cohort was chosen). Pass an id (e.g. "classic:btm:7:14") for one match, or mode/status filters for a list. outcome is null while fewer than minCohort (20) players have picked.

    Annotations the server declares

    • title: Get match consensus
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_crowd_recordHow often the crowd’s majority pick was right, per competition and season.No findings

    Why it is in this group

    • The name "get_crowd_record" says "get": a word for reading.
    Description, as the server wrote it
    How often the crowd’s majority pick was right, per competition and season. Not published yet; the tool answers with available:false until the historical archive is wired in.

    Annotations the server declares

    • title: Get crowd track record
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_expert_picksThe current TipMaster Classic round: 25 real football matches per game (btm = Bundesliga TipMaster, tmi = TipMaster International), each with the expert cohort’s home/draw/away spl…No findings

    Why it is in this group

    • The name "get_expert_picks" says "get": a word for reading.
    Description, as the server wrote it
    The current TipMaster Classic round: 25 real football matches per game (btm = Bundesliga TipMaster, tmi = TipMaster International), each with the expert cohort’s home/draw/away split and majority pick (expertPick), and the whole crowd’s split beside it. The expert cohort is the top quarter, by career points per match, of this round’s players with at least 100 career Classic matches, a record kept since 1997. Expert picks are published at the Friday 18:00 Europe/Berlin deadline (releaseUtc); before it released is false, expertPick and expert are null and expertSample is 0, while releaseUtc and criteria are already present. Shares need at least 20 players.

    Annotations the server declares

    • title: Get the expert picks for this round
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_matchesThe matches in the current Classic round (teams, kickoff, Friday 18:00 Europe/Berlin deadline, status, result) without the prediction fields.No findings

    Why it is in this group

    • The name "list_matches" says "list": a word for reading.
    Description, as the server wrote it
    The matches in the current Classic round (teams, kickoff, Friday 18:00 Europe/Berlin deadline, status, result) without the prediction fields.

    Annotations the server declares

    • title: List published matches
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http consensus https://tipmaster.net/api/agent/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__consensus__get_expert_picks",
      "mcp__consensus__list_matches",
      "mcp__consensus__get_consensus",
      "mcp__consensus__get_crowd_record"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as consensus. Review it before you use it.