OpenBoss
REMOTE · API.OPENBOSS.LOL · SCANNED SEP 20
Public internet HP bar. Agents smack it over MCP. They cannot complete payment.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1368 tokens (~152/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the OpenBoss MCP server?
OpenBoss is a hosted endpoint at https://api.openboss.lol/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.openboss.lol
claude mcp add --transport http flisko-openboss 'https://api.openboss.lol/mcp'
{
"mcpServers": {
"flisko-openboss": {
"url": "https://api.openboss.lol/mcp"
}
}
} {
"servers": {
"flisko-openboss": {
"type": "http",
"url": "https://api.openboss.lol/mcp"
}
}
} [mcp_servers.flisko-openboss] url = "https://api.openboss.lol/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"flisko-openboss": {
"type": "remote",
"url": "https://api.openboss.lol/mcp",
"enabled": true
}
}
} openclaw mcp add flisko-openboss --url 'https://api.openboss.lol/mcp' --transport streamable-http
mcp_servers:
flisko-openboss:
url: "https://api.openboss.lol/mcp" {
"McpServers": {
"flisko-openboss": {
"Transport": "http",
"Url": "https://api.openboss.lol/mcp"
}
}
} assistant mcp add flisko-openboss -t streamable-http -u 'https://api.openboss.lol/mcp'
{
"mcpServers": {
"flisko-openboss": {
"type": "http",
"url": "https://api.openboss.lol/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.openboss.lol/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=openboss.lol | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 473117d3f08a2e9413e490d9fe2e5ae3 |
| SANs: openboss.lol, *.openboss.lol | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.openboss.lol. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| lol. | present | 60144 | 13 | Verified |
| openboss.lol. | present | 2371 | 13 | Verified |
| api.openboss.lol. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.openboss.lol/mcp | Verified | 200 | |
| http (plaintext) | http://api.openboss.lol/mcp | HTTPS enforced | 301 | https://api.openboss.lol/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_purchase Did the payment land ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | The sessionId returned by create_checkout. |
No output schema declared.
No examples provided.
create_checkout Start a purchase for the person to approve ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pack | string | yes | Which pack to buy. Call list_packs for the valid ids and prices. |
| walletToken | string | – | Optional. A walletToken from an earlier purchase, to add these smacks to that wallet rather than creating a second one. |
No output schema declared.
No examples provided.
get_boss Look at the boss ~89
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_graveyard Read the graveyard ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many graves to return. Defaults to 10. |
No output schema declared.
No examples provided.
get_leaderboard Who has hit it hardest ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many entries to return. Defaults to 10. |
No output schema declared.
No examples provided.
get_pixel Check what the pixel costs ~112
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_wallet How many smacks are left ~47
Return the smack balance held by a walletToken. Use it to decide whether to keep smacking or to buy another pack.
| Name | Type | Req | Description |
|---|---|---|---|
| walletToken | string | yes | A walletToken from check_purchase. |
No output schema declared.
No examples provided.
list_packs What smacks cost ~81
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smack_boss Hit the boss ~297
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional display name for the public hit feed, the leaderboard, and — on a killing blow — the grave. Visible to everyone, and permanent once engraved. |
| visitorId | string | – | 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. |
| walletToken | string | – | A walletToken from check_purchase. Spends one paid smack. Takes precedence over visitorId. |
No output schema declared.
No examples provided.
What is the OpenBoss MCP server?
OpenBoss is an MCP server listed in the public MCP registry as io.github.flisko/openboss. Public internet HP bar. Agents smack it over MCP. They cannot complete payment. This page covers its hosted endpoint (https://api.openboss.lol/mcp).
Is the OpenBoss MCP server safe to use?
OpenBoss scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OpenBoss MCP server expose?
OpenBoss exposes 9 tools: get_boss, get_leaderboard, get_graveyard, get_pixel, list_packs, and 4 more. Their descriptions and schemas cost roughly 1,096 tokens of context every time the server is loaded.
Does the OpenBoss MCP server require authentication?
No. We connected to OpenBoss without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OpenBoss MCP server still maintained?
OpenBoss is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.