APICK Business
REMOTE · APICK.APP
Korean business, bid and real-estate analytics, parcel, building register and simple-auth data
Available components
Last scanned (13 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 25090 tokens (~234/item across 107 items; 107 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 42 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 107 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 107 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- New tool “kras_cert_jobs_create” functional
- New tool “kras_cert_jobs_pdf” functional
- New tool “kras_cert_jobs_status” functional
- 20 Nov 26 0
- Tool “registry_corporate_jobs_create” rewrote its description, which is the text the model reads security
- Tool “registry_realestate_jobs_create” rewrote its description, which is the text the model reads security
- Schema quality: 19176 → 24543 ▼ functional
- New tool “get_nps_career_cert” functional
- New tool “get_nps_contribution_unpaid_cert” functional
- New tool “get_nps_join_cert” functional
- New tool “get_nps_lump_sum_cert” functional
- New tool “get_nps_member_cert” functional
- New tool “get_nps_paid_cert” functional
- New tool “get_nps_pension_payment_cert” functional
- New tool “get_nps_pension_tax_cert” functional
- New tool “get_nps_rehabilitation_cert” functional
- New tool “req_nps_career_cert” functional
- New tool “req_nps_contribution_unpaid_cert” functional
- New tool “req_nps_join_cert” functional
- New tool “req_nps_lump_sum_cert” functional
- New tool “req_nps_member_cert” functional
- New tool “req_nps_paid_cert” functional
- New tool “req_nps_pension_payment_cert” functional
- New tool “req_nps_pension_tax_cert” functional
- New tool “req_nps_rehabilitation_cert” functional
- 19 Nov 26 −1
- Stability: pass → fail ▼ security
- Tool “registry_realestate_jobs_create” rewrote its description, which is the text the model reads security
- Tool “registry_realestate_search” rewrote its description, which is the text the model reads security
- “registry_realestate_jobs_create” reworded the description of “index” cosmetic
- “registry_realestate_jobs_create” reworded the description of “pin” cosmetic
- 18 Nov 26 0
- Tool “court_auction” rewrote its description, which is the text the model reads security
- Tool “ecommerce_registration” rewrote its description, which is the text the model reads security
- Tool “hipass_unpaid” rewrote its description, which is the text the model reads security
- Tool “registry_corporate_jobs_create” rewrote its description, which is the text the model reads security
- Tool “registry_corporate_search” rewrote its description, which is the text the model reads security
- Tool “registry_realestate_jobs_create” rewrote its description, which is the text the model reads security
- Tool “registry_realestate_search” rewrote its description, which is the text the model reads security
- Tool “vehicle_recall” rewrote its description, which is the text the model reads security
- New tool “debarred_company” functional
- New tool “std_price_commercial” functional
- New tool “tax_cert_verify” functional
- New tool “tax_invoice_third_party_check” functional
- 17 Nov 26 0
- New tool “ecommerce_registration” functional
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- “req_personal_income” added an optional parameter “telco” cosmetic
- “req_business_cert_bundle” added an optional parameter “telco” cosmetic
- “req_cash_receipt_deduction” added an optional parameter “telco” cosmetic
- “req_driving_license” added an optional parameter “telco” cosmetic
- “req_employment” added an optional parameter “telco” cosmetic
- “req_health_checkup” added an optional parameter “telco” cosmetic
- “req_hometax_biz_bundle” added an optional parameter “telco” cosmetic
- “req_hometax_bundle” added an optional parameter “telco” cosmetic
- “req_income_cert_bundle” added an optional parameter “telco” cosmetic
- “req_nps_bundle” added an optional parameter “telco” cosmetic
- “req_nps_career_history” added an optional parameter “telco” cosmetic
- “req_nps_deduction_cert” added an optional parameter “telco” cosmetic
- “req_nps_join_history” added an optional parameter “telco” cosmetic
- “req_tax_return_history” added an optional parameter “telco” cosmetic
- 9 Nov 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://apick.app/mcp/business
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apick.app | CN=YE2,O=Let's Encrypt,C=US | 20 Nov 2026 | 18 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 69a9648321547a1a8110e3ab96dc565d5c9 |
| SANs: apick.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apick.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| apick.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=(), serial=(), hid=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apick.app/mcp/business | Verified | 200 | |
| http (plaintext) | http://apick.app/mcp/business | HTTPS enforced | 308 | https://apick.app/mcp/business |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tax_cert_verify 국세 증명서 원본 확인 ~225
Verify a Korean tax certificate by the issuance number printed on it. 증명서에 인쇄된 발급번호(14자리)와 등록번호(주민 앞 6자리·사업자 10자리)로 납세증명서·소득금액증명·사업자등록증명 등 발급 사실을 확인합니다. 확인 결과는 verified(true 발급 사실 확인, false 발급 이력 없음)로 응답하며 증명서 원문은 돌려주지 않습니다. [호출당 40포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| cert_no | string | yes | 증명서의 발급번호 14자리. 연계문서는 첫 자리 T (예: 20260101123456) |
| txpr_clsf | string | – | 납세자 구분. 01 개인 02 사업자 (기본: 등록번호 길이로 자동 판정) |
| txpr_no | string | yes | 등록번호 — 주민등록번호 앞 6자리(개인) 또는 사업자등록번호 10자리 |
No output schema declared.
No examples provided.
tax_invoice_third_party_check 전자세금계산서 발급사실 확인 ~221
Verify the issuance of a Korean electronic tax invoice or e-statement (제3자 발급사실 조회). 공급자 사업자등록번호·공급받는자 등록번호·승인번호·작성일자·공급가액으로 전자세금계산서·전자계산서 발급 사실을 확인합니다. 확인 결과는 verified(true 발급 사실 확인, false 발급 이력 없음)로 응답하며 원문은 돌려주지 않습니다. [호출당 40포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| dmnr_no | string | yes | 공급받는자 등록번호 — 사업자 10자리 또는 주민 13자리 |
| etan | string | yes | 승인번호(24자리 이상, 공백·하이픈 제거 후 사용) |
| splr_no | string | yes | 공급자 사업자등록번호 10자리 |
| sum_amt | string | yes | 공급가액(원, 숫자만) |
| wrt_dt | string | yes | 작성일자 YYYYMMDD |
No output schema declared.
No examples provided.
vehicle_emission 배출가스 인증정보 조회 ~143
Look up Korean vehicle emission certification details by emission certification number. 배출가스인증번호로 인증일·차명·제조사·제작국가·연료·배출가스차종·배기량·엔진출력·변속기·공차중량·총중량과 인증 이력을 조회합니다. 입력은 차량번호가 아니라 배출가스인증번호이며, 배출가스 등급은 제공하지 않습니다. [호출당 60포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| cert_no | string | yes | 배출가스인증번호. 예: KMY-SY-13-24 |
No output schema declared.
No examples provided.
vehicle_model_info 차종별 차량정보 조회 ~468
Look up specifications of a Korean-market vehicle model (passenger cars and motorcycles/scooters) by brand, model name, model year and trim. 브랜드·차명·연식·등급으로 해당 차종(승용차와 오토바이·스쿠터 같은 이륜차)의 제원(배기량·연비·치수·타이어·소모품 규격 등), 사양, 등급 후보를 조회합니다. 차명 없이 부르면 브랜드·차종 목록을 돌려줍니다. 차명·등급 표기가 달라도 가장 비슷한 차종을 찾아 주며, 확신이 높으면 그 차종의 제원과 함께 추천(추천.자동선택, 추천.대안)을 알려주고 확신이 낮으면 제원 없이 후보만 알려줍니다. 제원 값은 표준 표기로만 내려갑니다(연료: 가솔린·디젤·LPG·전기·수소·하이브리드, 차체형상: 세단·SUV·MPV·스쿠터·네이키드 등, 구동방식: 전륜·후륜·2WD·AWD, 변속기: 자동 8단·DCT 7단·CVT, 에너지효율등급: 1~5등급, 여러 값은 "+"로 연결). [호출당 20포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| maker | string | – | 브랜드. 예: 현대, 기아, BMW, 렉서스 |
| model | string | – | 차명 또는 자유문 검색어. 예: 파나메라 gts 4인승 19년식, PANAMERA GTS 19년, 더 뉴 K5. 차명·연식·등급·승차인원을 비교하며 적합한 제원이 없으면 미과금. 비우면 차종 목록 |
| modelYear | string | – | 연식. 예: 2024, 24년식. model에 포함 가능하며 별도 값과 다르면 입력 오류 |
| trim | string | – | 등급·트림. 예: 프레스티지 |
No output schema declared.
No examples provided.
vehicle_recall 자동차 리콜 대상 조회 ~170
Check whether a Korean vehicle is subject to recalls or free repair campaigns by plate number or VIN. 차량번호 또는 차대번호(VIN) 중 하나로 리콜·무상점검수리 대상 여부와 건수, 리콜별 내용·시정 기간을 조회합니다. 리콜 대상이 아니어도(recall_target=false) 정상 조회로 과금됩니다. car_no 와 vin 은 둘 중 하나만 보냅니다. [호출당 60포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| car_no | string | – | 차량번호. 예: 12가3456, 서울12가3456 (vin 과 함께 보내지 않는다) |
| vin | string | – | 차대번호 17자리. 예: KMHXX00XXXX000000 (car_no 와 함께 보내지 않는다) |
No output schema declared.
No examples provided.
vehicle_tax_calc 자동차세 계산 ~177
Calculate the annual Korean automobile tax for a non-commercial passenger car from engine displacement and vehicle age. 비영업용 승용자동차의 배기량(cc)과 차령으로 연간 자동차세·지방교육세·합계를 계산합니다. 차령 3년차부터 매년 5%씩 최대 50%까지 경감합니다. 연납 공제·감면·영업용 차량은 계산하지 않습니다. [호출당 60포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| car_age_years | integer | – | 차령(년), 0~40. 생략하면 0 |
| cc | integer | yes | 배기량(cc), 50~10000 |
| year | integer | – | 과세연도(YYYY), 2011년부터 올해까지. 생략하면 올해 |
No output schema declared.
No examples provided.
venture_biz_info 벤처기업 정보조회 ~96
Look up venture company information of a Korean business, including financial statements and investment data. 벤처기업을 대상으로 사업자 정보, 대차대조표, 손익계산서, 투자정보, 벤처기업확인정보를 조회합니다. [호출당 40포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| biz_no | string | yes | 사업자등록번호 (숫자 10자리, 하이픈 제외) |
No output schema declared.
No examples provided.
How do I install the APICK Business MCP server?
APICK Business is a hosted endpoint at https://apick.app/mcp/business, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · apick.app
claude mcp add --transport http app-apick-business 'https://apick.app/mcp/business'
What is the APICK Business MCP server?
APICK Business is an MCP server listed in the public MCP registry as app.apick/business. Korean business, bid and real-estate analytics, parcel, building register and simple-auth data. This page covers its hosted endpoint (https://apick.app/mcp/business).
Is the APICK Business MCP server safe to use?
APICK Business scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the APICK Business MCP server expose?
APICK Business exposes 107 tools: biz_detail, venture_biz_info, ecommerce_registration, land_rt_price, req_pccc, and 102 more. Their descriptions and schemas cost roughly 25,090 tokens of context every time the server is loaded.
Does the APICK Business MCP server require authentication?
No. We connected to APICK Business without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the APICK Business MCP server still maintained?
APICK Business is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the APICK Business MCP server?
VerifyMCP ran 13 checks on APICK Business, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.