Robin Saige we check the tools AI agents call

freight intel

com.dropwatchhq/freight-intel

Freight carrier intel: new FMCSA authority feed, carrier lookup by DOT/MC, safety screen (CSA/SMS).

— the operator's own registry description reported

Publisher com.dropwatchhq · first seen 2026-08-12 · endpoint https://freight.dropwatchhq.com/mcp

allow
verdict
gateway
cluster
ok_tools
answers
9
tools served

Dependency rating derived

allow — gateway — safe to depend on

Cluster gateway · distinctiveness 0.209 (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
latency48 ms
vs populationfast
protocolstale
authopen
Use — can it use it?
tools9
vs populationmid
capabilities1
harnessA
Trust — can it rely on it?
identityfarm_member
servers on its host1
servers on its domain34
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

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

carrier_lookup carrier_risk_lookup chameleon_check new_authority_feed new_carriers regrade_list safety_screen search_carriers switch_signal

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 & specific9/9
has a description9/9
description is substantive9/9
parameters are typed9/9
parameters are described3/93/9

9 of 9 tools graded · 9 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

2024-11-05
protocol version
session model
1.0.0
server version freight-intel

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 (7 shown, 2026-08-12 → 2026-08-15). 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-15T05:10:09Zok_tools2001262024-11-05
2026-08-14T19:58:05Zok_tools200482024-11-05
2026-08-14T05:10:09Zok_tools2001112024-11-05
2026-08-13T05:10:09Zok_tools2001042024-11-05
2026-08-12T19:49:40Zok_tools2001352024-11-05
2026-08-12T17:50:21Zok_tools2005452024-11-05
2026-08-12T05:33:20Zok_tools200492024-11-05

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/com.dropwatchhq/freight-intel.svg)](https://robinsaige.com/s/com.dropwatchhq/freight-intel)

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