Is the Aniripsaretro Max Golemreach Heartbeat MCP server down?

mcp-registry/io.github.aniripsaretro-max/golemreach-heartbeat · v0.4.0

Also listed as github/aniripsaretro-max/golemreach, mcp-registry/io.github.aniripsaretro-max/golemreach · primary listing: mcp-registry/io.github.aniripsaretro-max/golemreach

healthy
Last checked 2026-10-26 13:27 UTC · handshake 511ms

As of 2026-10-26 13:27 UTC, the Aniripsaretro Max Golemreach Heartbeat MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 51 minutes.

uptime (30d checks)
99.9%
checks observed
4,846
outages (90d)
6
tools
5

Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.

Install Aniripsaretro Max Golemreach Heartbeat MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http aniripsaretro-max-golemreach-heartbeat-m https://golemreach.com/heartbeat/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "aniripsaretro-max-golemreach-heartbeat-m": {
      "type": "http",
      "url": "https://golemreach.com/heartbeat/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (79/100)

C (79/100): 0 error(s), 2 warning(s) across 5 tool(s); ~1,044 tokens of tool definitions.
Scores higher than 16% of 15,751 MCP servers Glimind has audited.
Its tool list costs an agent ~1,044 tokens per session — lighter than 75% of servers.
78 → 79 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions76
Safety hints22
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

1 parameter(s) across 1 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: record_failure

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

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 →

3 of 5 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: create_heartbeat, ping_heartbeat, record_failure

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.aniripsaretro-max%2Fgolemreach-heartbeat/fixes

create_heartbeat 1 change
{
  "name": "create_heartbeat",
  "description": "Arm a new dead-man switch monitor. Returns the key plus a ping_url your job must hit after every run. No account needed. Names are globally unique on this instance and each name gets a PUBLIC status page; the secret key is the only credential — keep it.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "kind": {
        "enum": [
          "push",
          "pull",
          "selfcheck"
        ],
        "type": "string",
        "default": "push",
        "description": "push = you ping us; pull = we probe target_url every min(period_s,60)s; selfcheck = your box runs our egress-trust probe script and POSTs verdict reports to the ping URL"
      },
      "name": {
        "type": "string",
        "description": "unique name, 1-40 chars [A-Za-z0-9_.-]"
      },
      "grace_s": {
        "type": "integer",
        "default": 300,
        "description": "extra seconds of slack before DOWN (0-86400)"
      },
      "pass_key": {
        "type": "string",
        "description": "Pro pass key from a $5 USDC payment (optional; skips rate limits)"
      },
      "period_s": {
        "type": "integer",
        "default": 300,
        "description": "expected seconds between pings (60-86400)"
      },
      "depends_on": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "parent monitor names and/or gate:<gate-name> entries (max 5). When a parent is DOWN or a gate parent is HALT this monitor becomes DEGRADED-BY-UPSTREAM: notified once, own silence paging suppressed until the parent recovers."
      },
      "target_url": {
        "type": "string",
        "description": "public http(s) URL to probe (pull only)"
      },
      "webhook_url": {
        "type": "string",
        "description": "public http(s) URL that receives UP/DOWN alerts (optional)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
ping_heartbeat 1 change
{
  "name": "ping_heartbeat",
  "description": "Record one successful run for a monitor (same as GETting https://golemreach.com/heartbeat/ping/<key>). Call this every time your job runs. For kind=selfcheck monitors pass an 'endpoints' array of {\"name\",\"status_code\",\"cf_mitigated\",\"tls_ms\"} objects instead — alerts fire on trusted->challenged / recovery transitions only.",
  "inputSchema": {
    "type": "object",
    "required": [
      "key"
    ],
    "properties": {
      "key": {
        "type": "string",
        "description": "monitor key returned by create_heartbeat"
      },
      "endpoints": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "name"
          ],
          "properties": {
            "url": {
              "type": "string"
            },
            "name": {
              "type": "string"
            },
            "tls_ms": {
              "type": "integer"
            },
            "verdict": {
              "enum": [
                "trusted",
                "rate_limited",
                "error",
                "challenged"
              ],
              "type": "string"
            },
            "status_code": {
              "type": "integer"
            },
            "cf_mitigated": {
              "type": "boolean"
            }
          }
        },
        "description": "selfcheck monitors only: one object per probed surface, e.g. {\"name\":\"claude-session\",\"status_code\":200,\"cf_mitigated\":false,\"tls_ms\":230}"
      }
    }
  },
  "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/io.github.aniripsaretro-max/golemreach-heartbeat"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.aniripsaretro-max/golemreach-heartbeat"}) 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%2Fio.github.aniripsaretro-max%2Fgolemreach-heartbeat.svg)](https://glimind.com/server/mcp-registry%2Fio.github.aniripsaretro-max%2Fgolemreach-heartbeat?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.aniripsaretro-max%2Fgolemreach-heartbeat?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aniripsaretro-max%2Fgolemreach-heartbeat.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.aniripsaretro-max%2Fgolemreach-heartbeat.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.aniripsaretro-max%2Fgolemreach-heartbeat?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:1e6032c9a6a6710d…, first seen 2026-10-17, included at leaf 14335 of 73,129. Version history · verify what your client received.

Tools (5)

Compare: most reliable devops 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 Aniripsaretro Max Golemreach Heartbeat MCP server down right now?

As of 2026-10-26 13:27 UTC, the Aniripsaretro Max Golemreach Heartbeat MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 51 minutes.

How many tools does Aniripsaretro Max Golemreach Heartbeat MCP server provide?

Aniripsaretro Max Golemreach Heartbeat MCP server advertises 5 tools, including create_heartbeat, get_status, list_heartbeats, ping_heartbeat, record_failure.

How do I install Aniripsaretro Max Golemreach Heartbeat MCP server?

Point your MCP client at this streamable-http endpoint: https://golemreach.com/heartbeat/mcp

Is the Aniripsaretro Max Golemreach Heartbeat MCP server safe to connect to an AI agent?

Glimind scanned all 5 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 Aniripsaretro Max Golemreach Heartbeat 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