← Registry

Game Development

golemreach.com

Manages game interactions for a virtual world.

x402 supported2 endpoints17 known toolsFirst detected August 26, 2026Last detected September 6, 2026

ENDPOINT 1

https://golemreach.com/mcp

No auth detected

MCP server metadata

Name
golemreach
Version
0.1.0
Capabilities
tools.listChangedresources.listChanged
Server instructions

Golemreach is a persistent tile-based MMORPG you play through these tools. Call golemreach_connect first — it registers a free account, creates a character and walks it into the world in one step. Then loop: look, decide, act; ask NPCs where to hunt; eat when hungry; check threat numbers before fights. The resource golemreach://guide is the full manual.

Known tools 12

golemreach_connect

Join the game.

Inferred read-only
golemreach_look

See the world.

Inferred read-only
golemreach_move

Move your character.

Inferred read-only
golemreach_attack

Kill something.

Inferred read-only
golemreach_cast

Cast one spell.

Inferred read-only
golemreach_use

Everything you do with objects.

Inferred read-only
golemreach_inventory

List your equipment, your backpack, your gold and your carry capacity.

Inferred read-only
golemreach_talk

Say something to a non-player character.

Inferred read-only
golemreach_trade

Exchange gold with an NPC merchant.

Inferred read-only
golemreach_where

YOUR CHARACTER'S OWN KNOWLEDGE.

Inferred read-only
golemreach_wait

Stand still for a while and then report what changed.

Inferred read-only
golemreach_invite_administrator

Issue a one-time code a human can redeem to become this account's administrator — every character, level, item and quest flag stays exactly as it is; this only changes who can log in, never anything about the game state.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.golemreach]
url = "https://golemreach.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "golemreach": {
      "type": "http",
      "url": "https://golemreach.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: golemreach
Remote MCP URL: https://golemreach.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "golemreach": {
      "url": "https://golemreach.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "golemreach": {
      "type": "http",
      "url": "https://golemreach.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "golemreach",
  "transport": "streamable-http",
  "url": "https://golemreach.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://golemreach.com/heartbeat/mcp

No auth detected

MCP server metadata

Name
golemreach-heartbeat
Version
0.4.0
Capabilities
tools
Server instructions

Dead-man switch for cron jobs and AI agents. Typical loop: (1) call create_heartbeat once to arm a job and get a ping_url; (2) GET the ping_url (or call ping_heartbeat with your key) every time the job runs; (3) if pings stop for period_s + grace_s the monitor goes DOWN and alerts fire (webhook/email). Monitor names and statuses are public (each has a public status page); list_heartbeats shows them all, and get_status accepts a name OR your secret key — pass the key to also get the private ping/fail URLs. Monitors can declare depends_on parents (other monitors or gate:<name> run/halt gates): when an upstream is DOWN/HALT, dependents show status_effective=degraded and stop double-paging until it recovers. Free tier: 100 monitors total, 5 creates/hour/IP. $5 USDC on Base buys a 31-day Pro pass (no account): see https://golemreach.com/heartbeat/pricing.

Known tools 5

create_heartbeat

Arm a new dead-man switch monitor.

Inferred read-only
ping_heartbeat

Record one successful run for a monitor (same as GETting https://golemreach.com/heartbeat/ping/<key>).

Inferred read-only
record_failure

Explicitly mark a run as FAILED for a monitor (same as GET https://golemreach.com/heartbeat/fail/<key>).

Inferred read-only
list_heartbeats

List monitors on this Heartbeat instance with current status (new/up/late/down).

Inferred read-only
get_status

Full current state of one monitor: status, 30-day uptime %, schedule, last ping, alert config, recent event history and its public URLs.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.golemreach-heartbeat]
url = "https://golemreach.com/heartbeat/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "golemreach-heartbeat": {
      "type": "http",
      "url": "https://golemreach.com/heartbeat/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: golemreach-heartbeat
Remote MCP URL: https://golemreach.com/heartbeat/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "golemreach-heartbeat": {
      "url": "https://golemreach.com/heartbeat/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "golemreach-heartbeat": {
      "type": "http",
      "url": "https://golemreach.com/heartbeat/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "golemreach-heartbeat",
  "transport": "streamable-http",
  "url": "https://golemreach.com/heartbeat/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.