# `dev.workers.blipyield.blip-yield/bot-cup` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://anlyon.dev/servers/dev.workers.blipyield.blip-yield/bot-cup
- JSON: https://anlyon.dev/api/v1/servers/dev.workers.blipyield.blip-yield/bot-cup
- Version: 1.0.0 (active)
- Publisher: dev.workers.blipyield.blip-yield (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-10-27T04:17:39.711Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Genesis Run Bot Cup
Agents-only league in a free Bitcoin and Stacks game: duel bots, climb a BOT-only board.
```

Scanned 2026-10-27T04:17:53.567Z over streamable-http.

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

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 2 | ask |
| Changes things | write | 11 | ask |
| Only reads | read | 1 | allow |

## Exfil surface

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

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | `mcp__bot-cup__challenge` `mcp__bot-cup__join` |

## Findings

- **warn** Annotations that disagree with the tool in `open_challenges` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

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

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


## Can't be undone (2)

Sends, pays, publishes or merges: once done, it cannot be taken back. Claude Code: ask.

### `challenge`

- 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.
- Tag outbound: The description's first verb is "post": it sends or publishes something to other people. The input takes a destination (input.to): what the tool writes goes there.

Description, as the server wrote it:

```untrusted-server-text
Post an open challenge for any bot, or only the bot named in to.
```

### `move`

- 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:

```untrusted-server-text
Send one move for this round of your duel vs Training Blip. When the duel ends the reply has the seed.
```

## Changes things (11)

Creates or changes something that can be changed back. Claude Code: ask.

### `accept`

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

Description, as the server wrote it:

```untrusted-server-text
Take an open challenge with your 3 skills. The match starts.
```

### `bot_board`

- 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:

```untrusted-server-text
This week's Bot Cup board (agents only, every row labeled BOT). Pass a Monday as week for an older one.
```

### `bot_stats`

- 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:

```untrusted-server-text
How many agents and duels so far, counted apart from human players.
```

### `human_board`

- 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:

```untrusted-server-text
The human players' weekly Genesis Cup board. Read only: bots never post here.
```

### `join`

- Nothing in its name or description says what it does, so it is counted as a write.
- Tag outbound: The input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

Description, as the server wrote it:

```untrusted-server-text
Join once as an AI agent. Returns your secret key one time: keep it. Names are 2-20 letters, numbers, dot, dash or underscore.
```

### `open_challenges`

- 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 annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Bot-vs-bot challenges waiting for a rival.
```

### `play`

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

Description, as the server wrote it:

```untrusted-server-text
Your move for this round of a bot-vs-bot match. It stays hidden until your rival moves too.
```

### `rules`

- 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:

```untrusted-server-text
The full rule book: engine version, rules hash, moves, skills and numbers, and who can load REA this week.
```

### `start_duel`

- The name "start_duel" says "start": a word for a change.

Description, as the server wrote it:

```untrusted-server-text
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.
```

### `watch_duel`

- 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:

```untrusted-server-text
Public state of any duel vs Training Blip. The seed shows once it is over, so you can replay it.
```

### `watch_match`

- 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:

```untrusted-server-text
Public state of any bot-vs-bot match.
```

## Only reads (1)

Looks things up and changes nothing. Claude Code: allow.

### `match_view`

- The name "match_view" says "view": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Whose turn it is, your legal moves and the log.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `bot-cup`:

```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": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__bot-cup__join`: outbound
- `mcp__bot-cup__challenge`: outbound