Openapi MCP server
{
"mcpServers": {
"goldpopcon-openapi": {
"command": "npx",
"args": [
"-y",
"@keumbang/goldpopcon-openapi-mcp@latest"
],
"env": {
"GOLDPOPCON_ACCESS_KEY": "<goldpopcon_access_key>",
"GOLDPOPCON_SECRET_KEY": "<goldpopcon_secret_key>"
}
}
}
}{
"mcpServers": {
"goldpopcon-openapi": {
"command": "npx",
"args": [
"-y",
"@keumbang/goldpopcon-openapi-mcp@latest"
],
"env": {
"GOLDPOPCON_ACCESS_KEY": "<goldpopcon_access_key>",
"GOLDPOPCON_SECRET_KEY": "<goldpopcon_secret_key>"
}
}
}
}{
"mcpServers": {
"goldpopcon-openapi": {
"command": "npx",
"args": [
"-y",
"@keumbang/goldpopcon-openapi-mcp@latest"
],
"env": {
"GOLDPOPCON_ACCESS_KEY": "<goldpopcon_access_key>",
"GOLDPOPCON_SECRET_KEY": "<goldpopcon_secret_key>"
}
}
}
}{
"servers": {
"goldpopcon-openapi": {
"command": "npx",
"args": [
"-y",
"@keumbang/goldpopcon-openapi-mcp@latest"
],
"env": {
"GOLDPOPCON_ACCESS_KEY": "${input:goldpopcon_access_key}",
"GOLDPOPCON_SECRET_KEY": "${input:goldpopcon_secret_key}"
}
}
},
"inputs": [
{
"id": "goldpopcon_access_key",
"type": "promptString",
"description": "Goldpopcon access key",
"password": true
},
{
"id": "goldpopcon_secret_key",
"type": "promptString",
"description": "Goldpopcon secret key",
"password": true
}
]
}{
"mcpServers": {
"goldpopcon-openapi": {
"command": "npx",
"args": [
"-y",
"@keumbang/goldpopcon-openapi-mcp@latest"
],
"env": {
"GOLDPOPCON_ACCESS_KEY": "<goldpopcon_access_key>",
"GOLDPOPCON_SECRET_KEY": "<goldpopcon_secret_key>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @keumbang/goldpopcon-openapi-mcpversion 0.3.1
What it does
MCP server for the Goldpopcon gold and silver trading API. It exposes endpoint documentation, generates JWT signing code in multiple languages, performs local request signing and verification, and optionally makes read-only API calls. Intended for developers integrating with Goldpopcon's trading platform.
- Look up API endpoint specifications, parameters, schemas, and rate limits for the Goldpopcon trading API.
- Generate complete signed request code in Python, JavaScript, Go, or curl for authenticating API calls.
- Debug JWT signing issues locally by signing requests with your credentials and verifying signatures match the server's expectations.
Tools this server exposes
| Tool | Does |
|---|---|
| list_endpoints | Returns list of available endpoints with permission scopes, idempotency, and rate limit buckets. |
| get_endpoint | Returns detailed specification for a single endpoint including parameters, body schema, request/response examples, and response codes. |
| list_error_codes | Returns table of error codes with status codes and retry guidance, including edge cases like insufficient balance returning 400. |
| signing_guide | Explains JWT signing procedure including query_hash branching, time claims, nonce, and idempotency requirements. |
| generate_signed_request | Generates complete signing request code in Python, JavaScript, Go, or curl for a given endpoint. |
| sign_request | Computes JWT locally with your credentials for debugging, returning the JWT, query_hash, and ready-to-use curl command. |
| verify_signature | Validates an existing JWT using server verification rules to diagnose 401 authentication failures. |
| call_api | Makes read-only live API calls (price quotes, balances, history) when enabled via environment variable; never calls write operations like trades or payouts. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.