goldprice.dev
REMOTE · API.GOLDPRICE.DEV · SCANNED AUG 3
Gold/silver/copper spot & futures, per-country dealer prices, options-implied probability surface.
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 8 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 804 tokens (~100/item across 8 items; 8 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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 · api.goldprice.dev
claude mcp add --transport http dev-goldprice-mcp https://api.goldprice.dev/v1/mcp/
[mcp_servers.dev-goldprice-mcp] url = "https://api.goldprice.dev/v1/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-goldprice-mcp": {
"type": "remote",
"url": "https://api.goldprice.dev/v1/mcp/",
"enabled": true
}
}
} openclaw mcp add dev-goldprice-mcp --url https://api.goldprice.dev/v1/mcp/ --transport streamable-http
mcp_servers:
dev-goldprice-mcp:
url: "https://api.goldprice.dev/v1/mcp/" {
"mcpServers": {
"dev-goldprice-mcp": {
"type": "http",
"url": "https://api.goldprice.dev/v1/mcp/"
}
}
} 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.
- 3 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.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 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.
- 28 Jul 26 +1
- Tool “get_physical_price” rewrote its description, which is the text the model reads security
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
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 3 Aug 2026 · Probed https://api.goldprice.dev/v1/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=goldprice.dev | CN=WE1,O=Google Trust Services,C=US | 26 Jun 2026 | 24 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | e6e0a81deec3503a13e94990b6a45432 |
| SANs: goldprice.dev, *.goldprice.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of api.goldprice.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| goldprice.dev. | 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://api.goldprice.dev/v1/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.goldprice.dev/v1/mcp/ | HTTPS enforced | 301 | https://api.goldprice.dev/v1/mcp/ |
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.
get_carat Get Karat-Gram Gold Prices ~135
Return per-gram gold (XAU) prices by karat purity — 24k, 22k, 21k, 20k, 18k, 16k, 14k, 10k — in a requested currency (default USD; the same 31 currencies get_spot_price serves). Jewelry-grade pricing computed from live XAU spot + ECB FX. FREE on every tier — no plan gate. Values are Decimal-formatted strings, quantized to the currency's ISO 4217 minor unit (JPY → whole numbers, USD → 2dp).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_forward_view Get Forward View ~77
Returns the multi-horizon futures settlement curve for a commodity (XAU, XAG, HG). Every populated horizon up to one year forward. Useful for bot builders and traders seeing the futures-implied path. See https://goldprice.dev/methodology#forward-view-layers for per-layer math.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_historical Get Historical Prices ~153
Return daily OHLCV bar history for a symbol. History depth is set automatically by your API key's plan — do NOT pass a tier argument (there is none): Free sees the last 30 days; Basic sees the last year; Pro unlocks full history back to 1996 (XAU/USD). Dates must be ISO 8601 (YYYY-MM-DD). Returns bars in date-descending order. volume is null for spot instruments (XAU/USD, XAG/USD); real for futures (GC, SI, HG) and ETFs (GLD).
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | — |
| limit | integer | — | — |
| symbol | string | yes | — |
| to_date | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_metadata Get Metadata ~47
Return provenance metadata for a symbol: aggregated sources, unit, methodology URL, staleness rules. Use for attribution and to document data lineage in downstream reports.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_physical_price Get Physical Dealer Gold Prices ~119
Return the latest per-country physical dealer/retail gold prices — real quotes from dealers, mints, and bullion benchmarks, NOT spot-derived arithmetic — with nullable premium_over_spot_bps per quote (null when live reference inputs are unavailable). `country` is an ISO 3166-1 alpha-2 code (e.g. ID, IN, AE, JP). Requires the Physical tier or higher; static sample responses for evaluation are in the docs at https://goldprice.dev/docs/physical.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_spot_price Get Spot Price ~56
Return the latest aggregated spot (or GC futures) price for one symbol. Price is a Decimal-formatted string; `is_stale` is true when aggregator detected source divergence or stale FX.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
list_commodities List Commodities ~43
Return the full list of symbols served by this API. Use before get_spot_price / get_historical / get_metadata when you don't know which symbols are supported.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_docs Search Docs ~67
Search the goldprice.dev FAQ corpus via BM25. Returns top-K matching questions + answers with relevance scores. Use before answering how-to / billing / auth questions so you cite the canonical text instead of guessing from training data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | — |
| query | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.