mcp-registry/io.github.flisko/openboss · v1.0.0
Also listed as github/flisko/openboss-mcp
As of 2026-10-20 17:33 UTC, the Flisko Openboss MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Public internet HP bar. Agents smack it over MCP. They cannot complete payment.
Claude Code
claude mcp add --transport http flisko-openboss-mcp-server https://api.openboss.lol/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"flisko-openboss-mcp-server": {
"type": "http",
"url": "https://api.openboss.lol/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~2,051 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.flisko%2Fopenboss/fixes
{
"name": "check_purchase",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"sessionId"
],
"properties": {
"sessionId": {
"type": "string",
"description": "The sessionId returned by create_checkout."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Did the payment land"
}{
"name": "create_checkout",
"description": "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",
"inputSchema": {
"type": "object",
"required": [
"pack"
],
"properties": {
"pack": {
"type": "string",
"description": "Which pack to buy. Call list_packs for the valid ids and prices."
},
"walletToken": {
"type": "string",
"description": "Optional. A walletToken from an earlier purchase, to add these smacks to that wallet rather than creating a second one."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Start a purchase for the person to approve"
}{
"name": "get_boss",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Look at the boss"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.flisko/openboss"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.flisko/openboss"}) over MCP.
smack_boss ~334 tokenscreate_checkout ~254 tokenscheck_purchase ~197 tokensget_pixel ~157 tokensget_graveyard ~145 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.flisko%2Fopenboss?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.flisko%2Fopenboss?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.flisko%2Fopenboss.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.flisko%2Fopenboss.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.flisko%2Fopenboss?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:808bb13b3b9cf7a1…, first seen 2026-10-17, included at leaf 2410 of 34,150. Version history · verify what your client received.
Compare: most reliable payments servers · most reliable data servers · most reliable finance servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 17:33 UTC, the Flisko Openboss MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Flisko Openboss MCP server advertises 9 tools, including check_purchase, create_checkout, get_boss, get_graveyard, get_leaderboard.
Point your MCP client at this streamable-http endpoint: https://api.openboss.lol/mcp
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.