MCP server for interacting with the Scryfall MTG API
Nothing to run from here
OpenBoss is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Public internet HP bar. Agents smack it over MCP. They cannot complete payment.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http openboss-mcp https://api.openboss.lol/mcp
# 2 — ask your agent for something these tools do
# get_boss, get_leaderboard, get_graveyard and 6 more
OpenBoss costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FLAll 1 server
flisko1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http openboss-mcp https://api.openboss.lol/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many entries to return. Defaults to 10. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many graves to return. Defaults to 10. |
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. S
No parameter schema on file.
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.
No parameter schema on file.
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pack | string | yes | Which pack to buy. Call list_packs for the valid ids and prices. |
| walletToken | string | no | Optional. A walletToken from an earlier purchase, to add these smacks to that wallet rather than creating a second one. |
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 wall
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sessionId | string | yes | The sessionId returned by create_checkout. |
Return the smack balance held by a walletToken. Use it to decide whether to keep smacking or to buy another pack.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| walletToken | string | yes | A walletToken from check_purchase. |
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. FR
| Parameter | Type | Required | Notes |
|---|---|---|---|
| walletToken | string | no | A walletToken from check_purchase. Spends one paid smack. Takes precedence over visitorId. |
| visitorId | string | no | For a free smack. A stable identifier you generate once and reuse so the free allowance is tracked. Any opaque string; a UUID is ideal. Nothing personal in it. |
| name | string | no | Optional display name for the public hit feed, the leaderboard, and — on a killing blow — the grave. Visible to everyone, and permanent once engraved. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OpenBoss or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish OpenBoss can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.