# com.goldpopcon/openapi-mcp (npm · @keumbang/goldpopcon-openapi-mcp)

금방 Open API MCP 서버 — 스펙 조회·JWT 서명 코드 생성·로컬 서명/검증

- Trust score: 87/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@keumbang/goldpopcon-openapi-mcp`: 87/100 (this document), [markdown](https://verifymcp.io/servers/com-goldpopcon-openapi-mcp/keumbang-goldpopcon-openapi-mcp.md), [page](https://verifymcp.io/servers/com-goldpopcon-openapi-mcp/keumbang-goldpopcon-openapi-mcp)

## Channel facts

- Registry: `npm`
- Package: `@keumbang/goldpopcon-openapi-mcp`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to keumbang/goldpopcon-openapi-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 33 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 46/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 844 tokens (~93/item across 9 items; 7 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.goldpopcon/openapi-mcp server?

com.goldpopcon/openapi-mcp runs locally as an npm package, launched with npx -y @keumbang/goldpopcon-openapi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-goldpopcon-openapi-mcp -- npx -y @keumbang/goldpopcon-openapi-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-goldpopcon-openapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@keumbang/goldpopcon-openapi-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-goldpopcon-openapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@keumbang/goldpopcon-openapi-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-goldpopcon-openapi-mcp -- npx -y @keumbang/goldpopcon-openapi-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-goldpopcon-openapi-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@keumbang/goldpopcon-openapi-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-goldpopcon-openapi-mcp --command npx --arg -y --arg @keumbang/goldpopcon-openapi-mcp
```

### Hermes

```yaml
mcp_servers:
  com-goldpopcon-openapi-mcp:
    command: "npx"
    args: ["-y", "@keumbang/goldpopcon-openapi-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-goldpopcon-openapi-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@keumbang/goldpopcon-openapi-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-goldpopcon-openapi-mcp -t stdio -c npx -a -y @keumbang/goldpopcon-openapi-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-goldpopcon-openapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@keumbang/goldpopcon-openapi-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 87, +1)

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

### 2026-09-18 (score 86, −3)

- [functional] Stability: pass → 0.80

### 2026-09-17 (score 89, +1)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 88, +1)

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

### 2026-09-13 (score 87, +1)

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

### 2026-09-11 (score 86, +1)

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

### 2026-09-09 (score 85, +1)

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

### 2026-09-07 (score 84, +1)

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

## MCP tools (7)

### `list_endpoints` (~80 tokens)

금방 Open API 엔드포인트 목록. 각 항목의 권한 스코프·멱등성 필요 여부·rate limit 버킷을 함께 준다.

Input parameters:

- `openApiOnly` (boolean): true 면 /open/* 만. 기본 true — 현재 스펙은 전부 /open/* 이라 결과가 같다

### `get_endpoint` (~67 tokens)

단일 엔드포인트 상세 — 설명, 파라미터, 요청 본문 스키마와 예제, 응답 상태, 권한·멱등성.

Input parameters:

- `operationId` (string, required): operationId. 예: buyAsset, getPrices, getPriceHistory

### `list_error_codes` (~56 tokens)

금방 Open API 에러 코드 표와 함정(잔액 부족은 400 P0001, 인증 실패는 error=null 401, 503 fail-closed 등). 상태 코드별 재시도 판단표 포함.

### `signing_guide` (~50 tokens)

요청 서명(JWT + query_hash) 절차. 개발자가 가장 많이 막히는 지점 — 업비트 예제를 그대로 옮기면 전부 401 이 나는 이유 포함.

### `generate_signed_request` (~220 tokens)

특정 엔드포인트를 호출하는 완결형 서명 코드를 생성한다(python/javascript/go/curl). query_hash 분기·멱등성 헤더를 메서드에 맞게 자동 반영.

Input parameters:

- `body`: POST 요청 본문 객체. 생략 시 스펙 예제 사용
- `language` (string, required): 생성 언어
- `operationId` (string, required): operationId. 예: sellAsset, getPriceHistory
- `pathParams` (object): 경로 파라미터. 예: {"asset":"gold"} (buy/sell)
- `query` (object): GET 쿼리 파라미터
- `server` (string): production | 임의 base url. 기본 production(스펙의 유일한 서버). 실거래 없이 시험하려면 server 가 아니라 operationId 를 demoBuyAsset/demoSellAsset 으로 바꾼다
- `ttlSeconds` (number): JWT 수명(초). 기본 30, 최대 60

### `sign_request` (~210 tokens)

실제 키로 요청 하나의 JWT 를 로컬 계산한다(디버깅용). secret_key 는 로컬에서만 쓰이고 어디로도 전송되지 않는다. 결과에 JWT·query_hash·바로 쓸 curl 을 준다.

Input parameters:

- `accessKey` (string, required): gpk_... 액세스 키
- `body`: POST 본문 객체. 생략 시 스펙 예제
- `operationId` (string, required)
- `pathParams` (object): 경로 파라미터. 예: {"asset":"gold"}
- `query` (object)
- `secretKey` (string, required): sk_... 시크릿 키. 로컬 계산에만 사용
- `server` (string): production | 임의 base url. 기본 production(스펙의 유일한 서버). 실거래 없이 시험하려면 operationId 를 demoBuyAsset/demoSellAsset 으로 바꾼다
- `ttlSeconds` (number)

### `verify_signature` (~151 tokens)

이미 만든 JWT 를 서버와 같은 순서로 로컬 검증해 401 원인을 짚는다. secret_key·전송할 본문/쿼리를 주면 query_hash 불일치까지 진단한다.

Input parameters:

- `method` (string, required)
- `query` (object): 실제 전송한(할) 쿼리. GET 계열 대조용
- `rawBody` (string): 실제 전송한(할) 본문 raw 문자열. POST 계열 query_hash 대조용
- `secretKey` (string, required): sk_... 시크릿 키
- `token` (string, required): 검증할 JWT(Bearer 접두사 있어도 됨)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-goldpopcon-openapi-mcp/keumbang-goldpopcon-openapi-mcp#diagnostics

## Score history

- 2026-09-21: 87
- 2026-09-20: 87
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 89
- 2026-09-16: 88
- 2026-09-15: 88
- 2026-09-14: 87
- 2026-09-13: 87
- 2026-09-12: 86
- 2026-09-11: 86
- 2026-09-10: 85
- 2026-09-09: 85
- 2026-09-08: 84
- 2026-09-07: 84
- 2026-09-06: 83
- 2026-09-05: 83
- 2026-09-04: 83
- 2026-09-03: 82
- 2026-09-02: 82
- 2026-09-01: 81
- 2026-08-31: 81
- 2026-08-30: 80
- 2026-08-29: 80
- 2026-08-28: 79
- 2026-08-27: 79
- 2026-08-26: 78
- 2026-08-25: 72
- 2026-08-24: 72
- 2026-08-23: 72

## Common questions

### What is the com.goldpopcon/openapi-mcp server?

com.goldpopcon/openapi-mcp is listed in the public MCP registry as com.goldpopcon/openapi-mcp. 금방 Open API MCP 서버, 스펙 조회·JWT 서명 코드 생성·로컬 서명/검증. This page covers its npm package (@keumbang/goldpopcon-openapi-mcp).

### Is the com.goldpopcon/openapi-mcp server safe to use?

com.goldpopcon/openapi-mcp scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 com.goldpopcon/openapi-mcp server expose?

com.goldpopcon/openapi-mcp exposes 7 tools: list_endpoints, get_endpoint, list_error_codes, signing_guide, generate_signed_request, and 2 more. Their descriptions and schemas cost roughly 834 tokens of context every time the server is loaded.

### Is the com.goldpopcon/openapi-mcp server still maintained?

com.goldpopcon/openapi-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 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 com.goldpopcon/openapi-mcp server under?

com.goldpopcon/openapi-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@keumbang/goldpopcon-openapi-mcp
- Socket report: https://socket.dev/npm/package/@keumbang/goldpopcon-openapi-mcp
- Repository: https://github.com/keumbang/goldpopcon-openapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-goldpopcon-openapi-mcp/keumbang-goldpopcon-openapi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-goldpopcon-openapi-mcp/keumbang-goldpopcon-openapi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-goldpopcon-openapi-mcp/keumbang-goldpopcon-openapi-mcp