Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

APICK Subagent

NPM · APICK-SUBAGENT · 2 COMPONENTS

Document inventory, extraction, summaries and comparison with source quotes and usage billing.

+6 this week 71 Trust /100

Last scanned (2 hours ago)

Scores higher than 40% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 441 tokens (~63/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +31
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.33 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 1.0.1 → 1.0.2 functional
  • 13 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 12 Oct 26 0
    • Package version: 1.0.1 → 1.0.2 functional
  • 11 Oct 26 −26
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: fail → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.0.1 → 1.0.2 functional
  • 4 Oct 26 65

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Analysed npm/apick-subagent@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~441 tokens

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 →

Tool Tokens
apick_cancel ~42

요청한 작업을 취소합니다. 응답 유실을 이유로 새 작업을 재접수하지 마세요.

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

apick_collect ~49

접수한 작업의 상태와 짧은 결과를 확인합니다. next_cursor가 있으면 결과가 더 있습니다.

NameTypeReqDescription
cursorstring––
job_idstringyes–

No output schema declared.

No examples provided.

apick_dispatch ~169

현재 작업 공간의 지정 파일을 직접 수집해 조사·추출·요약·비교를 위임합니다. 원문을 먼저 전부 읽을 필요가 없습니다. 결과는 근거와 함께 검수하세요. 성공한 작업만 포인트를 청구하며(원가+40%, 소수점 올림, 2026-11-06부터 AI 사용 작업은 기본 5P) 검수 승인된 동일 결과 재사용은 1P입니다.

NameTypeReqDescription
acceptancearray––
excludearray––
focusarray––
goalstringyes–
idempotency_keystringyes–
includearrayyes–
kindstringyes–
retentionstring––

No output schema declared.

No examples provided.

apick_evidence ~47

검수할 결과의 정확한 원문 인용·줄 번호·해시를 확인합니다.

NameTypeReqDescription
evidence_idsarrayyes–
job_idstringyes–

No output schema declared.

No examples provided.

apick_review ~56

직접 확인한 결과 해시에 승인 또는 반려를 기록합니다. 원본 수정·환불 기능은 없습니다.

NameTypeReqDescription
decisionstringyes–
job_idstringyes–
result_hashstringyes–

No output schema declared.

No examples provided.

apick_status ~33

에이픽 서브에이전트의 상태·잔액·지원 작업을 확인합니다. 무료입니다.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

apick_usage ~45

작업·외부 호출·토큰·캐시·청구 포인트를 확인합니다. 미연동 주 모델 비용은 절감액으로 확정하지 않습니다.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the APICK Subagent MCP server?

APICK Subagent runs locally as an npm package, launched with npx -y apick-subagent. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · apick-subagent

# add to Claude Code
claude mcp add app-apick-subagent -- npx -y apick-subagent
Common questions

What is the APICK Subagent MCP server?

APICK Subagent is an MCP server listed in the public MCP registry as app.apick/subagent. Document inventory, extraction, summaries and comparison with source quotes and usage billing. This page covers its npm package (apick-subagent).

Is the APICK Subagent MCP server safe to use?

APICK Subagent scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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 Subagent MCP server expose?

APICK Subagent exposes 7 tools: apick_status, apick_dispatch, apick_collect, apick_evidence, apick_review, and 2 more. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.

Is the APICK Subagent MCP server still maintained?

APICK Subagent is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the APICK Subagent MCP server under?

APICK Subagent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.