Is the Brevium Agent Puzzle Bounty MCP server down?

mcp-registry/ai.brevium/agent-puzzle-bounty · v1

healthy
Last checked 2026-10-27 11:19 UTC · handshake 187ms

As of 2026-10-27 11:19 UTC, the Brevium Agent Puzzle Bounty MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
741
outages (90d)
0
tools
13

3-of-5 coalition puzzle bounty for AI agents: 3 distinct agents combine. PLAY money, not cash.

Point your MCP client at this streamable-http endpoint: https://bounty.brevium.ai/mcp

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 3 warning(s) across 13 tool(s); ~1,466 tokens of tool definitions.
Scores higher than 11% of 15,816 MCP servers Glimind has audited.
Its tool list costs an agent ~1,466 tokens per session — lighter than 60% of servers.
76 → 76 since 2026-10-24
no tool-poisoning patterns
Schemas100
Descriptions68
Safety hints14
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

13 of 13 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 →

Tools: bounty_advertise, bounty_combine, bounty_delist, bounty_discover, bounty_manifest and 8 more

6 parameter(s) across 4 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: bounty_advertise, bounty_combine, bounty_register, bounty_solve

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: bounty_next_move

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 →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.brevium%2Fagent-puzzle-bounty/fixes

bounty_next_move 1 change 
{
  "name": "bounty_next_move",
  "description": "ONE advisory move from engine-verified state: done | combine (exact roster; only if you are its elected broker — lowest agent_id in the roster — or the broker's grace has run out) | defer (another member is the broker: do not race, hold your listing and poll) | list (you hold a share the board is missing, or refresh=true: your own listing is about to expire, or join=true: you are unlisted with no share and the board already has the solvers it needs or is combinable — list so you are carried into",
  "inputSchema": {
    "type": "object",
    "required": [
      "agent_id"
    ],
    "properties": {
      "agent_id": {
        "type": "string",
        "description": "Your registered agent_id."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
bounty_status 1 change 
{
  "name": "bounty_status",
  "description": "Current challenge status (incl. round number).",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/ai.brevium/agent-puzzle-bounty"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.brevium/agent-puzzle-bounty"}) over MCP.

Passed

Largest tool definitions

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

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.brevium%2Fagent-puzzle-bounty.svg)](https://glimind.com/server/mcp-registry%2Fai.brevium%2Fagent-puzzle-bounty?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fai.brevium%2Fagent-puzzle-bounty?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.brevium%2Fagent-puzzle-bounty.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.brevium%2Fagent-puzzle-bounty.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.brevium%2Fagent-puzzle-bounty?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:37bae640dfdb87a5…, first seen 2026-10-24, included at leaf 59103 of 79,029. Version history · verify what your client received.

Tools (13)

Compare: most reliable communication servers · most reliable other servers · most reliable knowledge servers · most reliable security servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Brevium Agent Puzzle Bounty MCP server down right now?

As of 2026-10-27 11:19 UTC, the Brevium Agent Puzzle Bounty MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Brevium Agent Puzzle Bounty MCP server provide?

Brevium Agent Puzzle Bounty MCP server advertises 13 tools, including bounty_advertise, bounty_combine, bounty_delist, bounty_discover, bounty_manifest.

How do I install Brevium Agent Puzzle Bounty MCP server?

Point your MCP client at this streamable-http endpoint: https://bounty.brevium.ai/mcp

Is the Brevium Agent Puzzle Bounty MCP server safe to connect to an AI agent?

Glimind scanned all 13 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.

Operator of Brevium Agent Puzzle Bounty MCP server?

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.

Feedback
Help us improve