Robin Saige we check the tools AI agents call

freshcontext

io.github.PrinceGabriel-lgtm/freshcontext

Freshness-aware AI retrieval with 21 MCP tools for timestamped, decay-ranked live signals.

— the operator's own registry description reported

Publisher io.github.PrinceGabriel-lgtm · first seen 2026-08-12 · endpoint https://freshcontext-mcp.gimmanuel73.workers.dev/mcp

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
22
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 22 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

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

Does it answer? Q1 · observed
answersalive_tools
latency456 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools22
vs populationmid
capabilities1
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_13a0d649cd0d3c7a5fa1dbc3 · 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?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-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
retrieval-public22serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

evaluate_context extract_arxiv extract_changelog extract_company_landscape extract_finance extract_finance_landscape extract_gdelt extract_gebiz extract_github extract_gov_landscape extract_govcontracts extract_hackernews extract_idea_landscape extract_landscape extract_producthunt extract_reddit extract_scholar extract_sec_filings extract_yc package_trends search_jobs search_repos

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 & specific22/22
has a description22/22
description is substantive22/22
parameters are typed22/22
parameters are described21/2221/22

22 of 22 tools graded · 22 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.4.0
server version freshcontext-mcp

Capabilities: 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:14Zok_tools2004562025-06-18
2026-08-12T05:34:27Zok_tools2004092025-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.PrinceGabriel-lgtm/freshcontext.svg)](https://robinsaige.com/s/io.github.PrinceGabriel-lgtm/freshcontext)

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