Robin Saige we check the tools AI agents call

ContextLayer

io.github.DotNova/context-layer

Intelligent context infrastructure for AI teams: knowledge graph, sessions, tasks, documents.

— the operator's own registry description reported

Publisher io.github.DotNova · first seen 2026-08-12 · endpoint https://api.dotnova.io/mcp

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
62
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency391 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools62
vs populationhigh
capabilities2
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_0ecc67ba4cabe2652507c107 · 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?rich-slow-solo · 1 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
action26changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public25serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified8not classifiable from its textTier-1 only until its tools describe themselves
computational1deterministic transformsself-checkable by re-computation and known-answer tests
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

accept_org_invite add_task_dependency add_team_member assign_task create_position create_project create_sprint create_task create_team delete_document delete_position delete_project delete_task delete_team delete_user end_session find_documents get_context get_context_routing get_document get_live_activity get_my_stats get_org_stats get_project_status get_session_details get_team_details invite_user link_task_session link_team_project list_colleagues list_notifications list_pending_invites list_positions list_project_members list_project_teams list_projects list_sessions list_sprints list_tasks list_teams log_activity log_trace log_traces_batch mark_notification_read move_task_to_sprint remove_task_dependency remove_team_member remove_user_from_org search_entities set_context_routing setup_organization start_session unassign_task unlink_team_project update_org update_position update_project update_task update_team update_user upload_document whoami

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 & specific62/62
has a description62/62
description is substantive59/6259/62
parameters are typed56/6256/62
parameters are described62/62

62 of 62 tools graded · 62 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
1.1.0
server version rmcp

Capabilities: 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:00Zok_tools2003912025-06-18
2026-08-12T05:34:15Zok_tools2003942025-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.DotNova/context-layer.svg)](https://robinsaige.com/s/io.github.DotNova/context-layer)

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