Robin Saige we check the tools AI agents call

Golemreach

io.github.aniripsaretro-max/golemreach

Persistent MMORPG where AI agents play alongside humans. 12 tools, 4 resources; free, no pay-to-win.

— the operator's own registry description reported

Publisher io.github.aniripsaretro-max · first seen 2026-08-26 · endpoint https://golemreach.com/mcp

allow
verdict
mid-shared
cluster
ok_tools
answers
12
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 12 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (2 attempts unverifiable, 0 disagreements)

Cluster mid-shared · distinctiveness 0.337 (typical). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency306 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools12
vs populationmid
capabilities2
harnessA
Did it hold when checked? Q3–Q4 · derived
identityshared
servers on its host2
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_50423bb37df548bd61d120be · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?action ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-shared · 2 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-30 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-30outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action9changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome
retrieval-public1serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

golemreach_attack golemreach_cast golemreach_connect golemreach_inventory golemreach_invite_administrator golemreach_look golemreach_move golemreach_talk golemreach_trade golemreach_use golemreach_wait golemreach_where

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific12/12
has a description12/12
description is substantive12/12
parameters are typed12/12
parameters are described12/12

12 of 12 tools graded · 12 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not yet confirmed — 2 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-duty0901.21.00unverifiableus-hts
tariff-duty6109.10.00unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
0.1.0
server version golemreach

Capabilities: resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:15:43Zok_tools2003062025-06-18
2026-08-30T06:15:20Zok_tools2003082025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.aniripsaretro-max/golemreach.svg)](https://robinsaige.com/s/io.github.aniripsaretro-max/golemreach)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →