Robin Saige we check the tools AI agents call

neurogenesis

io.github.jdhart81/neurogenesis

Developmental agents + Wu Wei compute routing: evolve from outcomes, route to cheapest reliable.

— the operator's own registry description reported

Publisher io.github.jdhart81 · first seen 2026-08-12 · endpoint https://mcp.viridisconservation.com/neurogenesis/mcp

allow
verdict
gateway
cluster
ok_tools
answers
14
tools served

Dependency rating derived

allow
allow — gateway · kind unknown · V n/a
allow — because answers ●, 14 tools legible (band B) ●, no confirmed drift in 2 probes ●; not yet checked: truth (1 attempts unverifiable, 0 disagreements)

Cluster gateway · distinctiveness 0.411 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency216 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools14
vs populationmid
capabilities4
harnessB
Did it hold when checked? Q3–Q4 · derived
identityfarm_member
servers on its host30
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_8b38103f263614bf1b8d1a62 · 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?gateway — 2 probes ●evidence ↓
Q2What is it?kind unknown ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?gateway · 30 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-12 → 2026-08-14). 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-12outcomefirst 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
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified4not classifiable from its textTier-1 only until its tools describe themselves
retrieval-public3serves public factstruth-checkable against a public source — the V-ladder applies in full
predictive2claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome
computational1deterministic transformsself-checkable by re-computation and known-answer tests

Tools last seen observed

best_next_steps compute_efficiency_report create_agent delete_agent describe_agent export_state get_agent get_ledger import_state list_agents record_route_outcome register_compute_profile route_task submit_evaluation

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 B — usable, with rough edges.

legibility checktools passingok
name is clear & specific14/14
has a description14/14
description is substantive13/1413/14
parameters are typed14/14
parameters are described2/142/14

14 of 14 tools graded · 14 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 — 1 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.28.1
server version neurogenesis-agent

Capabilities: experimental prompts resources tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:38Zok_tools2002162025-06-18
2026-08-12T05:34:51Zok_tools2001632025-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.jdhart81/neurogenesis.svg)](https://robinsaige.com/s/io.github.jdhart81/neurogenesis)

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