Robin Saige we check the tools AI agents call

APICK Business

app.apick/business

Korean business registry, corporate info, parcel tracking, validation APIs

— the operator's own registry description reported

Publisher app.apick · first seen 2026-08-12 · endpoint https://apick.app/mcp/business

allow
verdict
mid-slow-shared
cluster
ok_tools
answers
16
tools served

Dependency rating derived

allow — mid-slow-shared — safe to depend on

Cluster mid-slow-shared · distinctiveness 0.368 (moderate). 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
latency814 ms
vs populationslow
protocolcurrent
authopen
Use — can it use it?
tools16
vs populationmid
capabilities1
harnessA
Trust — can it rely on it?
identityshared
servers on its host9
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

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

biz_detail check_email_valid check_pccc check_phone_valid check_spam_number get_car_flooding get_car_scrap get_pccc holiday_info info land_rt_price parcel_tracking parcel_tracking_auto req_pccc search_juso venture_biz_info

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 & specific16/16
has a description16/16
description is substantive16/16
parameters are typed16/16
parameters are described16/16

16 of 16 tools graded · 16 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.0.1
server version app.apick/business

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 (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
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:57:43Zok_tools2008142025-06-18
2026-08-12T05:33:00Zok_tools2009352025-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/app.apick/business.svg)](https://robinsaige.com/s/app.apick/business)

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