Robin Saige we check the tools AI agents call

Gov Auctions

io.github.pipeworx-io/gov-auctions

Government Auctions MCP — physical-asset auctions (surplus, seized, forfeited,

— the operator's own registry description reported

Publisher io.github.pipeworx-io · first seen 2026-08-12 · endpoint https://gateway.pipeworx.io/gov-auctions/mcp

allow
verdict
gateway
cluster
ok_tools
answers
36
tools served

Dependency rating derived

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

Cluster gateway · distinctiveness 0.812 (unusual). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency28 ms
vs populationfast
protocolcurrent
authopen
Can it be used? Q4 · observed
tools36
vs populationhigh
capabilities3
harnessA
Did it hold when checked? Q3–Q4 · derived
identityfarm_member
servers on its host1312
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_e33e6c784e97cd235f6d3d51 · 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?gateway — 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?gateway · 1312 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-public21serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
predictive4claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome
computational3deterministic transformsself-checkable by re-computation and known-answer tests
generative2creates contentno answer key exists; disclosure + stability checks, never truth verdicts
orchestration2routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)

Tools last seen observed

ai_visibility_check ask_pipeworx ask_pipeworx_beta ask_pipeworx_grounded auction_lot_details auctions_closing_soon auctions_coverage auctions_search auctions_sold_comps bet_research compare_entities deep_research discover_tools entity_profile forget generate_llms_txt list_subscriptions pipeworx_feedback pipeworx_trending polymarket_arbitrage polymarket_edge_tracker polymarket_edges polymarket_fill_risk polymarket_kalshi_spread recall recent_alerts recent_changes remember resolve_entity scan_competitor_ai_presence scan_dependency search_within subscribe suggest_questions unsubscribe validate_claim

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 & specific36/36
has a description36/36
description is substantive36/36
parameters are typed36/36
parameters are described36/36

36 of 36 tools graded · 36 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 pipeworx-gateway

Capabilities: prompts 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-14T20:00:02Zok_tools200282025-06-18
2026-08-12T05:35:17Zok_tools200412025-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.pipeworx-io/gov-auctions.svg)](https://robinsaige.com/s/io.github.pipeworx-io/gov-auctions)

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