# @keumbang/goldpopcon-openapi-mcp

금방(Keumbang) Open API 코딩 어시스턴트 MCP 서버 — 스펙 조회 · JWT 서명 코드 생성 · 로컬 서명/검증

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.3.1
- **Author:** Unknown
- **License:** MIT
- **npm:** @keumbang/goldpopcon-openapi-mcp
- **Source:** https://github.com/keumbang/goldpopcon-openapi-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 34 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-01T10:03:04.944Z
- **Version scanned:** 0.3.1
- **CVEs:** none found by OSV at scan time

## Tools

8 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `list_endpoints` — 금방 Open API 엔드포인트 목록. 각 항목의 권한 스코프·멱등성 필요 여부·rate limit 버킷을 함께 준다.
- `get_endpoint` — 단일 엔드포인트 상세 — 설명, 파라미터, 요청 본문 스키마와 예제, 응답 상태, 권한·멱등성.
- `list_error_codes` — 금방 Open API 에러 코드 표와 함정(잔액 부족은 400 P0001, 인증 실패는 error=null 401, 503 fail-closed 등). 상태 코드별 재시도 판단표 포함.
- `signing_guide` — 요청 서명(JWT + query_hash) 절차. 개발자가 가장 많이 막히는 지점 — 업비트 예제를 그대로 옮기면 전부 401 이 나는 이유 포함.
- `generate_signed_request` — 특정 엔드포인트를 호출하는 완결형 서명 코드를 생성한다(python/javascript/go/curl). query_hash 분기·멱등성 헤더를 메서드에 맞게 자동 반영.
- `sign_request` — 실제 키로 요청 하나의 JWT 를 로컬 계산한다(디버깅용). secret_key 는 로컬에서만 쓰이고 어디로도 전송되지 않는다. 결과에 JWT·query_hash·바로 쓸 curl 을 준다.
- `verify_signature` — 이미 만든 JWT 를 서버와 같은 순서로 로컬 검증해 401 원인을 짚는다. secret_key·전송할 본문/쿼리를 주면 query_hash 불일치까지 진단한다.
- `call_api` — 골드팝콘 Open API를 실제로 호출한다(조회 전용 · production 고정). getPrices/getBalances/getPriceHistory/getOrderPreview/getTradeHistory 만 허용 — 자금 이동 엔드포인트는 불가. 키는 env(GOLDPOPCON_

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"goldpopcon-openapi\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@keumbang/goldpopcon-openapi-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40keumbang%2Fgoldpopcon-openapi-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40keumbang%2Fgoldpopcon-openapi-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40keumbang%2Fgoldpopcon-openapi-mcp
- HTML page: https://forgeregistry.com/registry/%40keumbang%2Fgoldpopcon-openapi-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.