com.goldpopcon/openapi-mcp
NPM · @KEUMBANG/GOLDPOPCON-OPENAPI-MCP
금방 Open API MCP 서버 — 스펙 조회·JWT 서명 코드 생성·로컬 서명/검증
Available components
Last scanned (35 minutes ago)
Scores higher than 71% of npm servers
Category Finance and Payments
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to keumbang/goldpopcon-openapi-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 79 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability46
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 844 tokens (~93/item across 9 items; 7 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
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 8 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 5 Nov 26 −2
- Stability: pass → 0.87 functional
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.93 functional
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 6 Nov 2026 · Analysed npm/@keumbang/goldpopcon-openapi-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | keumbang/goldpopcon-openapi-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/keumbang/goldpopcon-openapi-mcp/.github/workflows/publish.yml@refs/tags/v0.3.1 |
| Rekor log index | 2501106180 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:56a82ccca878a493b89081e545bb2c0272080a101afd1ad124840438a387a50d1fd98052af318792b10ed2b4082d2bd1d0055f2539f57fd325737be47 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
generate_signed_request ~220
특정 엔드포인트를 호출하는 완결형 서명 코드를 생성한다(python/javascript/go/curl). query_hash 분기·멱등성 헤더를 메서드에 맞게 자동 반영.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | POST 요청 본문 객체. 생략 시 스펙 예제 사용 |
| language | string | yes | 생성 언어 |
| operationId | string | yes | 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 |
No output schema declared.
No examples provided.
get_endpoint ~67
단일 엔드포인트 상세 — 설명, 파라미터, 요청 본문 스키마와 예제, 응답 상태, 권한·멱등성.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | operationId. 예: buyAsset, getPrices, getPriceHistory |
No output schema declared.
No examples provided.
list_endpoints ~80
금방 Open API 엔드포인트 목록. 각 항목의 권한 스코프·멱등성 필요 여부·rate limit 버킷을 함께 준다.
| Name | Type | Req | Description |
|---|---|---|---|
| openApiOnly | boolean | – | true 면 /open/* 만. 기본 true — 현재 스펙은 전부 /open/* 이라 결과가 같다 |
No output schema declared.
No examples provided.
list_error_codes ~56
금방 Open API 에러 코드 표와 함정(잔액 부족은 400 P0001, 인증 실패는 error=null 401, 503 fail-closed 등). 상태 코드별 재시도 판단표 포함.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sign_request ~210
실제 키로 요청 하나의 JWT 를 로컬 계산한다(디버깅용). secret_key 는 로컬에서만 쓰이고 어디로도 전송되지 않는다. 결과에 JWT·query_hash·바로 쓸 curl 을 준다.
| Name | Type | Req | Description |
|---|---|---|---|
| accessKey | string | yes | gpk_... 액세스 키 |
| body | – | – | POST 본문 객체. 생략 시 스펙 예제 |
| operationId | string | yes | – |
| pathParams | object | – | 경로 파라미터. 예: {"asset":"gold"} |
| query | object | – | – |
| secretKey | string | yes | sk_... 시크릿 키. 로컬 계산에만 사용 |
| server | string | – | production | 임의 base url. 기본 production(스펙의 유일한 서버). 실거래 없이 시험하려면 operationId 를 demoBuyAsset/demoSellAsset 으로 바꾼다 |
| ttlSeconds | number | – | – |
No output schema declared.
No examples provided.
signing_guide ~50
요청 서명(JWT + query_hash) 절차. 개발자가 가장 많이 막히는 지점 — 업비트 예제를 그대로 옮기면 전부 401 이 나는 이유 포함.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_signature ~151
이미 만든 JWT 를 서버와 같은 순서로 로컬 검증해 401 원인을 짚는다. secret_key·전송할 본문/쿼리를 주면 query_hash 불일치까지 진단한다.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | – |
| query | object | – | 실제 전송한(할) 쿼리. GET 계열 대조용 |
| rawBody | string | – | 실제 전송한(할) 본문 raw 문자열. POST 계열 query_hash 대조용 |
| secretKey | string | yes | sk_... 시크릿 키 |
| token | string | yes | 검증할 JWT(Bearer 접두사 있어도 됨) |
No output schema declared.
No examples provided.
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.
npm · @keumbang/goldpopcon-openapi-mcp
claude mcp add com-goldpopcon-openapi-mcp -- npx -y @keumbang/goldpopcon-openapi-mcp
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 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 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 6 November 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.
What did VerifyMCP test on the com.goldpopcon/openapi-mcp server?
VerifyMCP ran 15 checks on com.goldpopcon/openapi-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about com.goldpopcon/openapi-mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.