APICK Finance
REMOTE · APICK.APP · SCANNED AUG 18
Korean bank account verification: holder name lookup, 1 KRW deposit, bank codes
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 348 tokens (~116/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · apick.app
claude mcp add --transport http app-apick-finance https://apick.app/mcp/finance
[mcp_servers.app-apick-finance] url = "https://apick.app/mcp/finance"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-apick-finance": {
"type": "remote",
"url": "https://apick.app/mcp/finance",
"enabled": true
}
}
} openclaw mcp add app-apick-finance --url https://apick.app/mcp/finance --transport streamable-http
mcp_servers:
app-apick-finance:
url: "https://apick.app/mcp/finance" {
"mcpServers": {
"app-apick-finance": {
"type": "http",
"url": "https://apick.app/mcp/finance"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 62
First indexed and scored.
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 18 Aug 2026 · Probed https://apick.app/mcp/finance
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=apick.app | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 24 Apr 2026 | 8 Nov 2026 | RSA 2048 | SHA256-RSA | ff9cd226add88096b646ade956162508 |
| SANs: apick.app, www.apick.app | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
| CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 1 Feb 2010 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | 1fd6d30fca3ca51a81bbc640e35032d |
DNSSEC insecure
Validation of apick.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| apick.app. | absent | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apick.app/mcp/finance | Verified | 200 | |
| http (plaintext) | http://apick.app/mcp/finance | HTTPS enforced | 301 | https://apick.app/mcp/finance |
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.
account_realname 계좌 예금주 실명 조회 ~131
Look up the account holder name of a Korean bank account. 대한민국 은행 계좌의 예금주명을 조회합니다. 송금 전 예금주 확인 등에 사용합니다. bank_code 또는 bank_name 중 하나는 입력해야 합니다. [호출당 60포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| account_num | string | yes | 계좌번호 (숫자만, 하이픈 제외) |
| bank_code | string | – | 은행 코드 (bank_code Tool로 조회 가능, 예: 004) |
| bank_name | string | – | 은행명 (예: 국민). bank_code 대신 입력 가능 |
No output schema declared.
No examples provided.
bank_code 은행코드 조회 ~55
List Korean bank codes and names. 대한민국 은행 코드·은행명 전체 목록을 반환합니다. transfer_1won, account_realname Tool의 bank_code 입력값을 찾을 때 사용합니다. 무료입니다. [무료]
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
transfer_1won 1원 인증 ~162
Send a 1 KRW verification deposit to a Korean bank account and return the 4-character verification code printed on the transaction. 대한민국 은행 계좌로 1원을 입금해 적요에 표시되는 인증코드를 반환합니다. 계좌 실소유 확인(1원 인증) 절차에 사용합니다. bank_code 또는 bank_name 중 하나는 입력해야 합니다. [호출당 60포인트]
| Name | Type | Req | Description |
|---|---|---|---|
| account_num | string | yes | 계좌번호 (숫자만, 하이픈 제외) |
| bank_code | string | – | 은행 코드 (bank_code Tool로 조회 가능, 예: 004) |
| bank_name | string | – | 은행명 (예: 국민). bank_code 대신 입력 가능 |
No output schema declared.
No examples provided.