Verify a Company
dev.hatchloop/company-verification
Verify a company on GLEIF LEI and SEC EDGAR, screen sanctions. No key; quota-free data.
— the operator's own registry description reported
Publisher dev.hatchloop · first seen 2026-09-02 · endpoint https://hatchloop.dev/mcp/company-verification
Dependency rating derived
allow — alive & usable · retrieval-public ● · V3W answer key in hand ◐
Cluster stale-mid-slow-shared · distinctiveness 0.565 (moderate). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.
🔏 Signed receipt rr_77bebf5ac259929d948215ff · 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.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
History observed
Every probe we made, oldest → newest (1 shown, 2026-09-06 → 2026-09-06). 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)
| date | type | what changed |
|---|---|---|
| 2026-09-06 | outcome | first 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 →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| retrieval-public | 6 | serves public facts | truth-checkable against a public source — the V-ladder applies in full |
| computational | 1 | deterministic transforms | self-checkable by re-computation and known-answer tests |
Tools last seen observed
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 check | tools passing | ok |
|---|---|---|
| name is clear & specific | 7/7 | ✓ |
| has a description | 7/7 | ✓ |
| description is substantive | 7/7 | ✓ |
| parameters are typed | 7/7 | ✓ |
| parameters are described | 4/7 | 4/7 |
7 of 7 tools graded · 7 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
2/2 answers agree with the published primary source.
| claim class | key | verdict | primary source |
|---|---|---|---|
| OFAC SDN screening (vs the official list) | ISLAMIC REVOLUTIONARY GUARD CORPS | agrees | ofac-sdn |
| OFAC SDN screening (vs the official list) | MAERSK LINE | agrees | ofac-sdn |
Protocol conformance observed
Capabilities: logging prompts resources tools
Drift observed
No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-09-06T06:13:21Z | ok_tools | 200 | 476 | 2024-11-05 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/dev.hatchloop/company-verification)
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.
Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →