Robin Saige we check the tools AI agents call

Company Intel

com.timzinin.api/company-intel

9 pay-per-call company intel tools over MCP. Free discovery, calls settle in USDC on Base (x402).

— the operator's own registry description reported

Publisher com.timzinin.api · first seen 2026-08-12 · endpoint https://api.timzinin.com/mcp/company-intel

allow
verdict
mid-shared
cluster
ok_tools
answers
19
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency339 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools19
vs populationmid
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identityshared
servers on its host9
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_adc1c91e6a1d2dd46b4b0bb8 · 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-shared · 9 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-public9serves 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
unclassified4not classifiable from its textTier-1 only until its tools describe themselves
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)

Tools last seen observed

company-hiring-radar company-lookup company-registry-enricher competitor-change-rollup counterparty-risk-rollup email-verifier funding-alert funding-round-tracker hiring-trend-index intent-signal-aggregator layoff-tracker lead-list-qualifier litigation-check new-company-detector patent-monitor pricing_info sanctions-screening sanctions-update-alert website-contact-extractor

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 & specific19/19
has a description19/19
description is substantive19/19
parameters are typed19/19
parameters are described19/19

19 of 19 tools graded · 19 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 yet confirmed — 2 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
OFAC SDN screening (vs the official list)ISLAMIC REVOLUTIONARY GUARD CORPSunverifiableofac-sdn
OFAC SDN screening (vs the official list)MAERSK LINEunverifiableofac-sdn

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version zinin-m2m-hub-company-intel

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:58:35Zok_tools2003392025-06-18
2026-08-12T05:33:49Zok_tools2003062025-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.timzinin.api/company-intel.svg)](https://robinsaige.com/s/com.timzinin.api/company-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