APICK MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to APICK Korean data, OCR and media tools with hosted MCP access: Do tool availability and metered identity-document operations retain clear evidence and privacy boundaries?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Accessing a broad Korean data/AI API catalog from agents through one MCP bridge.

What we know

APICK MCP exposes Korean business/identity/OCR/logistics/search/conversion/AI/media APIs through a local stdio bridge or hosted remote MCP.

Maintenance / activity evidence

apick-mcp 4.0.0 published 2026-10-05T13:58:48.479Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
API-key/account scope and selected sub-server. Writes: Paid API calls; Generate media; Verification/conversion operations.
APICK API key.
Sensitive access: Identity documents, Business/finance data, OCR input, API key

A broad paid API catalog mixes low-risk lookup with sensitive identity/financial/document operations; scope the enabled server/tool set.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do tool availability and metered identity-document operations retain clear evidence and privacy boundaries?

The bounded review of the publisher's documented APICK Korean data, OCR and media tools with hosted MCP access and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

A broad paid API catalog mixes low-risk lookup with sensitive identity/financial/document operations; scope the enabled server/tool set.
API-key/account scope and selected sub-server.
APICK API key.
Requests can include identity/business documents, OCR content, finance/account-verification data, search prompts and generated media.
Reviewed write actions: Paid API calls; Generate media; Verification/conversion operations
Sensitive access: Identity documents, Business/finance data, OCR input, API key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Canonical repository identity
Stable tool count at exact observed version
Tool count changes frequently across releases; do not hardcode an old count.
Most API calls require a funded/credentialed APICK account.
Horizontal catalog spans very different sensitivity/cost classes.

Original activity observations

apick-mcp 4.0.0 published 2026-10-05T13:58:48.479Z

Technical identity

npm/apick-mcp

Exact implementation source: https://www.npmjs.com/package/apick-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:apick-mcp
Service endpoint: https://apick.app/mcp/all

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 7, 2026

Package registry ↗
apick-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Remote API uses bearer key; stdio fallback `npx -y apick-mcp --server all`; identity/PII operations can be billed
APICK_API_KEY is required to make authenticated tool calls but not to discover tools. Remote uses Authorization Bearer; local stdio uses APICK_API_KEY; cannot label remote auth as required environment variable.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Remote API uses bearer key; stdio fallback `npx -y apick-mcp --server all`; identity/PII operations can be billed | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions · Review before use
```
claude mcp add --transport http apick https://apick.app/mcp/all --header "Authorization: Bearer <KEY>"
```
Configure / authenticate
MCP100 setup guide
Publisher hosted HTTP is primary. APICK_API_KEY optional for discovery but required for authenticated tool calls.
Check connection
Suggested check
Check client tools; do not run paid identity checks or document conversion as test.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `apick`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove apick

Official Documentation & Sources

What it does

APICK MCP exposes Korean business/identity/OCR/logistics/search/conversion/AI/media APIs through a local stdio bridge or hosted remote MCP.

Capability: Data & Databases
Resource type: MCP Server
Best fit: Accessing a broad Korean data/AI API catalog from agents through one MCP bridge.

Representative uses

Business registry and identity verification
OCR/document extraction
Parcel tracking and web intelligence
Image/video/TTS/LLM/file-conversion APIs

Limitations

Tool count changes frequently across releases; do not hardcode an old count.
Most API calls require a funded/credentialed APICK account.
Horizontal catalog spans very different sensitivity/cost classes.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: APICK API key.
Permissions: API-key/account scope and selected sub-server.
Data handling: Requests can include identity/business documents, OCR content, finance/account-verification data, search prompts and generated media.
Cost: usage_based
Risk and cautions: A broad paid API catalog mixes low-risk lookup with sensitive identity/financial/document operations; scope the enabled server/tool set.

Access scope and cautions

Write actions: Paid API calls Generate media Verification/conversion operations
Sensitive access: Identity documents Business/finance data OCR input API key
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Business registry and identity verification; OCR/document extraction; Parcel tracking and web intelligence; Image/video/TTS/LLM/file-conversion APIs.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y apick-mcp --server business. Recorded endpoint: https://apick.app/mcp/all. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: APICK_API_KEY; APICK_MCP_SERVER optional. No configuration values are supplied here. Prerequisites: Node/npm. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: APICK API key for most calls.

Can it modify data or perform write operations?

Documented write actions include: Paid API calls; Generate media; Verification/conversion operations. Recorded permission boundary: API-key/account scope and selected sub-server.

What data-handling boundary should I consider?

Requests can include identity/business documents, OCR content, finance/account-verification data, search prompts and generated media. Recorded sensitive-access context: Identity documents; Business/finance data; OCR input; API key.

What limitations and risks should I check before use?

A broad paid API catalog mixes low-risk lookup with sensitive identity/financial/document operations; scope the enabled server/tool set. Tool count changes frequently across releases; do not hardcode an old count. Most API calls require a funded/credentialed APICK account. Horizontal catalog spans very different sensitivity/cost classes. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Is this an official MCP?

APICK is listed as First-party MCP in MCP100’s current evidence.