Should my agent depend on the MCP server io.github.eidetic-works/nucleus?

Verdict: allow — mid-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

nucleus

io.github.eidetic-works/nucleus

Sovereign Agent OS — Persistent Memory, Governance & Compliance for AI Agents.

— the operator's own registry description reported

Publisher io.github.eidetic-works · first seen 2026-08-12 · endpoint https://relay.nucleusos.dev/mcp

allow

verdict

mid-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-slow-solo — safe to depend on

Cluster mid-slow-solo · distinctiveness 0.737 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency786 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools28

vs populationmid

capabilities6

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_0a54b0104e0058ada2e9c702 · 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.

Tools last seen

nucleus_agents nucleus_audit nucleus_ccr_arm nucleus_delegate nucleus_engrams nucleus_features nucleus_federation nucleus_governance nucleus_infra nucleus_lane_feedback nucleus_lane_init nucleus_lane_start nucleus_lane_status nucleus_lane_stop nucleus_next_message nucleus_orchestration nucleus_plan_execute nucleus_plan_import nucleus_plan_list nucleus_relay nucleus_relay_subscribe nucleus_route nucleus_sessions nucleus_slots nucleus_sync nucleus_tasks nucleus_telemetry nucleus_wakeup_wait

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 check	tools passing	ok
name is clear & specific	28/28	✓
has a description	28/28	✓
description is substantive	28/28	✓
parameters are typed	28/28	✓
parameters are described	11/28	11/28

28 of 28 tools graded · 28 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 in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

3.4.4

server version Nucleus Brain

Capabilities: experimental extensions logging prompts resources tools

Drift

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

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)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:31Z	ok_tools	200	786	2025-06-18
2026-08-12T05:34:44Z	ok_tools	200	852	2025-06-18

Watch or embed this verdict

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.eidetic-works/nucleus.svg)](https://robinsaige.com/s/io.github.eidetic-works/nucleus)

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