Skip to content

OpenBoss MCP server

io.github.flisko/openbossfliskostreamable-httpv1.0.0Scanned

Public internet HP bar. Agents smack it over MCP. They cannot complete payment.

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

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 OpenBoss MCP server can do

The OpenBoss MCP server is published by the GitHub account flisko. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (check_purchase) and create or change data (2 tools: create_checkout and smack_boss), but cannot delete data. 6 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 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.

9 tools

Can't be undone 1Claude Code: ask
  • check_purchaseGiven the sessionId from create_checkout, report whether the person has paid yet.No findings

    Why it is in this group

    • The name "check_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Given the sessionId from create_checkout, report whether the person has paid yet. Once paid, returns a walletToken and the smack balance it holds — pass that token to smack_boss to spend it. Poll every few seconds after sending someone to the checkout URL; card payments settle asynchronously, so "not paid yet" shortly afterwards is normal rather than a failure. Keep the walletToken: it IS the wallet, there is no account behind it, and whoever holds it holds the smacks.
Changes things 2Claude Code: ask
  • create_checkoutOpen a Stripe Checkout Session for one smack pack and return its URL.No findings

    Why it is in this group

    • The name "create_checkout" says "create": a word for a change.
    Description, as the server wrote it
    Open a Stripe Checkout Session for one smack pack and return its URL. THIS DOES NOT PAY — hand the URL to the person, who opens it and enters their own card. That page is where they are told smacks are not refundable and that there are no prizes and no payouts, which is why it cannot be skipped. Then poll check_purchase with the returned sessionId until it reports paid, and you get a walletToken to spend with smack_boss. Pass an existing walletToken to top that same wallet up instead of starting a new one.
  • smack_bossLand one smack on the current boss and return the damage dealt and the remaining hit points.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
    Land one smack on the current boss and return the damage dealt and the remaining hit points. One swing per call — call it repeatedly to keep hitting. PAID: pass walletToken (from check_purchase) to spend one smack from that wallet. Paid hits are the real thing — they can crit, they take the momentum multiplier, and only a paid hit can land the killing blow and put a name on the grave forever. FREE: pass visitorId instead and it costs nothing. Three per visitorId — the count is held for about thirty days — then FREE_EXHAUSTED, which is the limit working and not a fault. It is NOT an hourly allowance: waiting does not give them back. A free smack can never land the killing blow and free damage is capped per boss, so the engraving stays with somebody who paid for it. Pass one or the other. If both arrive, the wallet is spent.
Only reads 6Show 6 read-only tools
  • get_bossReturn the world boss everyone is currently hitting: its name, lore, tier, current and maximum hit points, active affixes, the live momentum multiplier, and how much damage has bee…No findings

    Why it is in this group

    • The name "get_boss" says "get": a word for reading.
    Description, as the server wrote it
    Return the world boss everyone is currently hitting: its name, lore, tier, current and maximum hit points, active affixes, the live momentum multiplier, and how much damage has been dealt. Use this to answer "what is the boss right now", "how much health is left", or before deciding whether to smack it. One boss exists at a time and everyone in the world shares it.
  • get_graveyardReturn bosses that have already been killed, newest first, each with the display name of whoever landed the killing blow.No findings

    Why it is in this group

    • The name "get_graveyard" says "get": a word for reading.
    Description, as the server wrote it
    Return bosses that have already been killed, newest first, each with the display name of whoever landed the killing blow. That engraving is permanent and is the only thing anyone actually wins. Use this for "who has killed a boss", "how many bosses have died", or to look up a past boss.
  • get_leaderboardReturn the damage leaderboard for the current boss — display names and total damage, highest first — together with the most recent hits.No findings

    Why it is in this group

    • The name "get_leaderboard" says "get": a word for reading.
    Description, as the server wrote it
    Return the damage leaderboard for the current boss — display names and total damage, highest first — together with the most recent hits. Use this to answer "who is winning", "who has done the most damage", or to see whether a particular name is on the board. Resets when the boss dies.
  • get_pixelReturn the current state of The Pixel (thepixel.lol): who owns it, what they paid, its colour, the minimum price to take it, and recent ownership history.No findings

    Why it is in this group

    • The name "get_pixel" says "get": a word for reading.
    Description, as the server wrote it
    Return the current state of The Pixel (thepixel.lol): who owns it, what they paid, its colour, the minimum price to take it, and recent ownership history. Use this for "who owns the pixel" or "what would it cost to buy it". BUYING IT IS NOT AVAILABLE AS A TOOL — a purchase needs a person at the payment page, because a bid that loses a simultaneous takeover is charged in full and refunds nothing. Send the human to https://thepixel.lol to buy.
  • get_walletReturn the smack balance held by a walletToken.No findings

    Why it is in this group

    • The name "get_wallet" says "get": a word for reading.
    Description, as the server wrote it
    Return the smack balance held by a walletToken. Use it to decide whether to keep smacking or to buy another pack.
  • list_packsReturn every smack pack for sale: id, price in US dollars, how many smacks it buys, and any bonus.No findings

    Why it is in this group

    • The name "list_packs" says "list": a word for reading.
    Description, as the server wrote it
    Return every smack pack for sale: id, price in US dollars, how many smacks it buys, and any bonus. Call this before create_checkout so you can tell the person what they are about to pay. Prices are final — no VAT or tax is added at checkout. Also reports the free allowance, so you can mention that trying it costs nothing.

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 or outbound.

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 out0
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 20, 2026, 19:04 UTC, unchanged since Oct 22, 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
3
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 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.openboss.lol/mcp: tools/list returned 9 tools to an anonymous client, including check_purchase (irreversible), create_checkout (write), smack_boss (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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 openboss https://api.openboss.lol/mcp
claude mcp add --transport http openboss https://api.openboss.lol/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__openboss__get_boss",
      "mcp__openboss__get_leaderboard",
      "mcp__openboss__get_graveyard",
      "mcp__openboss__get_pixel",
      "mcp__openboss__list_packs",
      "mcp__openboss__get_wallet"
    ],
    "ask": [
      "mcp__openboss__create_checkout",
      "mcp__openboss__check_purchase",
      "mcp__openboss__smack_boss"
    ],
    "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 openboss. Review it before you use it.

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/io.github.flisko/openboss/verify?hash=59332cc3b336fd3eef89c9d4fa55ea0595927abb2baed8d25cf38c8a0ef8cd0d" | jq -e '.changed == false'

Pinned hash 59332cc3b336, from Nov 19, 2026, 17:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.flisko/openboss/changes.xml

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

Badge

Anlyon Radar badge for io.github.flisko/openboss
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.flisko/openboss.svg)](https://radar.anlyon.com/servers/io.github.flisko/openboss)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.

OpenBoss MCP server: questions and answers

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

Is the OpenBoss MCP server safe?

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

Can the OpenBoss MCP server delete data?

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

Can the OpenBoss MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: check_purchase.

What tools does the OpenBoss MCP server have?

9 tools: 1 irreversible, 2 write, 6 read. check_purchase, create_checkout, smack_boss, get_boss, get_leaderboard, get_graveyard, get_pixel, list_packs and 1 more.

Does the OpenBoss MCP server need sign-in or OAuth?

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

Does the OpenBoss MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the OpenBoss MCP server changed its tools?

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