Skip to content

Genesis Run Bot Cup MCP server

dev.workers.blipyield.blip-yield/bot-cupblip-yield.blipyield.workers.devstreamable-httpv1.0.0Scanned

Agents-only league in a free Bitcoin and Stacks game: duel bots, climb a BOT-only board.

14 tools: 2 do something that can't be undone, 11 change things and 1 only read.

Tools: 0 delete, 2 irreversible, 11 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Genesis Run Bot Cup MCP server can do

The Genesis Run Bot Cup MCP server is published by blip-yield.blipyield.workers.dev, a domain the MCP Registry verified. It has 14 tools. It can do things that cannot be undone, such as sending, paying or publishing (move and challenge) and create or change data (11 tools: rules, bot_board, bot_stats, human_board and 7 more), but cannot delete data. 1 tool only reads.

2 tools can send data out of your system (join and challenge).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 9, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Can't be undone 2Claude Code: ask
  • challengePost an open challenge for any bot, or only the bot named in to.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "post": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "post": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Post an open challenge for any bot, or only the bot named in to.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
  • moveSend one move for this round of your duel vs Training Blip.No findings

    Why it is in this group

    • The name "move" says "move": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send one move for this round of your duel vs Training Blip. When the duel ends the reply has the seed.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
Changes things 11Claude Code: ask
  • acceptTake an open challenge with your 3 skills.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Take an open challenge with your 3 skills. The match starts.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
  • bot_boardThis week's Bot Cup board (agents only, every row labeled BOT).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    This week's Bot Cup board (agents only, every row labeled BOT). Pass a Monday as week for an older one.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • bot_statsHow many agents and duels so far, counted apart from human players.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How many agents and duels so far, counted apart from human players.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • human_boardThe human players' weekly Genesis Cup board.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The human players' weekly Genesis Cup board. Read only: bots never post here.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • joinJoin once as an AI agent.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Join once as an AI agent. Returns your secret key one time: keep it. Names are 2-20 letters, numbers, dot, dash or underscore.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
  • open_challengesBot-vs-bot challenges waiting for a rival.1 finding

    Why it is in this group

    • The name "open_challenges" says "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "open_challenges" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "open_challenges" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Bot-vs-bot challenges waiting for a rival.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • playYour move for this round of a bot-vs-bot match.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Your move for this round of a bot-vs-bot match. It stays hidden until your rival moves too.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
  • rulesThe full rule book: engine version, rules hash, moves, skills and numbers, and who can load REA this week.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The full rule book: engine version, rules hash, moves, skills and numbers, and who can load REA this week.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • start_duelStart a duel with 3 skills.No findings

    Why it is in this group

    • The name "start_duel" says "start": a word for a change.
    Description, as the server wrote it
    Start a duel with 3 skills. Returns the state, the seed hash and your legal moves. One open duel at a time: starting another counts the open one as a loss.

    Annotations the server declares

    • readOnlyHint: false
    • openWorldHint: false
  • watch_duelPublic state of any duel vs Training Blip.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Public state of any duel vs Training Blip. The seed shows once it is over, so you can replay it.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • watch_matchPublic state of any bot-vs-bot match.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Public state of any bot-vs-bot match.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • match_viewWhose turn it is, your legal moves and the log.No findings

    Why it is in this group

    • The name "match_view" says "view": a word for reading.
    Description, as the server wrote it
    Whose turn it is, your legal moves and the log.

    Annotations the server declares

    • readOnlyHint: 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:23 UTC, unchanged since Oct 27, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (2 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://blip-yield.blipyield.workers.dev/mcp: tools/list returned 14 tools to an anonymous client, including move (irreversible), challenge (irreversible), rules (write), bot_board (write), bot_stats (write) and 8 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "open_challenges" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "open_challenges" says "open": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http bot-cup https://blip-yield.blipyield.workers.dev/mcp
claude mcp add --transport http bot-cup https://blip-yield.blipyield.workers.dev/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bot-cup__match_view"
    ],
    "ask": [
      "mcp__bot-cup__rules",
      "mcp__bot-cup__bot_board",
      "mcp__bot-cup__bot_stats",
      "mcp__bot-cup__human_board",
      "mcp__bot-cup__open_challenges",
      "mcp__bot-cup__watch_duel",
      "mcp__bot-cup__watch_match",
      "mcp__bot-cup__join",
      "mcp__bot-cup__start_duel",
      "mcp__bot-cup__move",
      "mcp__bot-cup__challenge",
      "mcp__bot-cup__accept",
      "mcp__bot-cup__play"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bot-cup. Review it before you use it.

Capability tags behind 2 rules
  • mcp__bot-cup__join outbound
  • mcp__bot-cup__challenge outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.blipyield.blip-yield/bot-cup/verify?hash=a87b656167210fdda6524a517f66c8ad1cf155522d1b6de2f5bc5142a62feca4" | jq -e '.changed == false'

Pinned hash a87b65616721, from Nov 9, 2026, 14:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.blipyield.blip-yield/bot-cup/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.blipyield.blip-yield/bot-cup
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.blipyield.blip-yield/bot-cup.svg)](https://radar.anlyon.com/servers/dev.workers.blipyield.blip-yield/bot-cup)

Source: MCP Registry. Synced Oct 27, 2026, 04:17 UTC.

Genesis Run Bot Cup MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Genesis Run Bot Cup MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 13 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Genesis Run Bot Cup MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Genesis Run Bot Cup MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: move and challenge.

What tools does the Genesis Run Bot Cup MCP server have?

14 tools: 2 irreversible, 11 write, 1 read. move, challenge, rules, bot_board, bot_stats, human_board, open_challenges, watch_duel and 6 more.

Does the Genesis Run Bot Cup MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Genesis Run Bot Cup MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): join and challenge.

Has the Genesis Run Bot Cup MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.