Robin Saige we check the tools AI agents call

Auralogs

ai.auralogs/auralogs

Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.

— the operator's own registry description reported

Publisher ai.auralogs · first seen 2026-08-12 · endpoint https://mcp.auralogs.ai/mcp

allow
verdict
stale-mid-solo
cluster
ok_tools
answers
7
tools served

Dependency rating derived

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

Cluster stale-mid-solo · distinctiveness 0.162 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency105 ms
vs populationtypical
protocolbehind
authopen
Use — can it use it?
tools7
vs populationmid
capabilities1
harnessB
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

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

get_analysis get_log get_project list_analyses list_logs list_projects search_logs

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 & specific7/7
has a description7/7
description is substantive7/7
parameters are typed7/7
parameters are described1/71/7

7 of 7 tools graded · 7 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-03-26
protocol version
session model
0.1.0
server version auralogs

Capabilities: 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)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:57:34Zok_tools2001052025-03-26
2026-08-12T05:32:52Zok_tools2001272025-03-26

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/ai.auralogs/auralogs.svg)](https://robinsaige.com/s/ai.auralogs/auralogs)

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