Robin Saige we check the tools AI agents call

Datalastic Vessel Tracking & Maritime Intelligence

com.datalastic/vessel-tracking

Vessel tracking for 750,000+ ships, with ownership, inspections, port records, routes, and more.

— the operator's own registry description reported

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

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

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency412 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools25
vs populationmid
capabilities2
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_de3a315e9d94edc9958db9c0 · 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 — 7 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 (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

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-public15serves public factstruth-checkable against a public source — the V-ladder applies in full
action5changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative2creates contentno answer key exists; disclosure + stability checks, never truth verdicts
computational1deterministic transformsself-checkable by re-computation and known-answer tests
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

estimated_vessel_position find_ports find_vessels get_port get_vessel get_vessel_history get_vessel_info get_vessel_pro get_vessels_bulk get_vessels_in_radius get_weather intel_casualties intel_class intel_companies intel_drydock intel_engine intel_info intel_inspections intel_ownership intel_report_request intel_spd report_list report_request report_status sea_route

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 & specific25/25
has a description25/25
description is substantive25/25
parameters are typed25/25
parameters are described25/25

25 of 25 tools graded · 25 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 datalastic-mcp

Capabilities: logging 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-15T05:10:09Zok_tools2004572025-06-18
2026-08-14T19:58:02Zok_tools2004122025-06-18
2026-08-14T05:10:09Zok_tools2004942025-06-18
2026-08-13T05:10:09Zok_tools2004352025-06-18
2026-08-12T19:49:40Zok_tools2004732025-06-18
2026-08-12T17:50:21Zok_tools20011322025-06-18
2026-08-12T05:33:18Zok_tools2004132025-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/com.datalastic/vessel-tracking.svg)](https://robinsaige.com/s/com.datalastic/vessel-tracking)

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