Robin Saige we check the tools AI agents call

cache proxy

io.github.Ainode-tech/cache-proxy

LLM caching proxy (x402 USDC on Base) - exact + semantic cache. Free health.

— the operator's own registry description reported

Publisher io.github.Ainode-tech · first seen 2026-08-12 · endpoint https://cache.api.ainode.tech/mcp

allow
verdict
thin-shared
cluster
ok_tools
answers
2
tools served

Dependency rating derived

allow — thin-shared — safe to depend on

Cluster thin-shared · distinctiveness 0.311 (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
latency151 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools2
vs populationlow
capabilities1
harnessA
Trust — can it rely on it?
identityshared
servers on its host1
servers on its domain4
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

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

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. This server's 2 tools, classified, with what checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action1changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public1serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen

cache_query health

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 & specific2/2
has a description2/2
description is substantive2/2
parameters are typed2/2
parameters are described2/2

2 of 2 tools graded · 2 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
0.1.0
server version cache-proxy

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:58:54Zok_tools2001512025-06-18
2026-08-12T05:34:08Zok_tools2001462025-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.Ainode-tech/cache-proxy.svg)](https://robinsaige.com/s/io.github.Ainode-tech/cache-proxy)

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