Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

goldprice.dev

REMOTE · API.GOLDPRICE.DEV · SCANNED SEP 25

Gold/silver/copper spot & futures, per-country dealer prices, options-implied probability surface.

0 this week 75 Trust /100
Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 982 tokens (~109/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
Install

How do I install the goldprice.dev MCP server?

goldprice.dev is a hosted endpoint at https://api.goldprice.dev/v1/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.goldprice.dev

# add to Claude Code
claude mcp add --transport http dev-goldprice-mcp 'https://api.goldprice.dev/v1/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-goldprice-mcp": {
      "url": "https://api.goldprice.dev/v1/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-goldprice-mcp": {
      "type": "http",
      "url": "https://api.goldprice.dev/v1/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-goldprice-mcp]
url = "https://api.goldprice.dev/v1/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-goldprice-mcp": {
      "type": "remote",
      "url": "https://api.goldprice.dev/v1/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-goldprice-mcp --url 'https://api.goldprice.dev/v1/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-goldprice-mcp:
    url: "https://api.goldprice.dev/v1/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-goldprice-mcp": {
      "Transport": "http",
      "Url": "https://api.goldprice.dev/v1/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add dev-goldprice-mcp -t streamable-http -u 'https://api.goldprice.dev/v1/mcp/'
// mcp.json
{
  "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.

Changelog

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.

  • 25 Sept 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
  • 17 Sept 26 0
    • Tool “get_spot_price” rewrote its description, which is the text the model reads security
  • 15 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_historical” rewrote its description, which is the text the model reads security
  • 14 Sept 26 0
    • Tool “get_historical” rewrote its description, which is the text the model reads security
    • “get_historical” added an optional parameter “interval” cosmetic
  • 26 Aug 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
  • 25 Aug 26 0
    • A breaking change shipped without a version bump: still 3.2.4 ▼ security
    • Tool “start_checkout” was removed ▼ security
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 900 → 804 ▲ functional
  • 19 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 804 → 900 ▼ functional
    • New tool “start_checkout” functional
  • 11 Aug 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
Diagnostics

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 25 Sept 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 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA256 f0e9c0fb96fb26040e9bf15796b026b2
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

Background: What to check on a remote MCP endpoint →

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

Background: How OAuth 2.1 works in the 2026 MCP spec →

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/
MCP tools · 9 exposed · ~839 tokens

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 →

Tool Tokens
get_carat ~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).

NameTypeReqDescription
currencystring––

Structured output declared, but exposes no named fields.

No examples provided.

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.

NameTypeReqDescription
assetstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_historical ~204

Return OHLCV bar history for a symbol at 1m, 5m, 15m, 30m, 1h, 2h, 4h, or 1d (default). Intraday intervals require Pro. 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; Physical 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, XCU/USD); real for futures (GC, SI, HG) and ETFs (GLD).

NameTypeReqDescription
from_datestringyes–
intervalstring––
limitinteger––
symbolstringyes–
to_datestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

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.

NameTypeReqDescription
symbolstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_physical_price ~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.

NameTypeReqDescription
countrystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_spot_price ~86

Return the latest aggregated spot (or GC futures) price for one symbol. Price is a Decimal-formatted string. Latest USD spot price/bid/ask use nearest half-up rounding: XAU 2 decimal places, XAG 3, HG 4. `is_stale` is true when aggregator detected source divergence or stale FX.

NameTypeReqDescription
symbolstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

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 ~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.

NameTypeReqDescription
limitinteger––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

start_checkout ~61

Open a direct billing URL for an explicitly selected eligible plan: a one-hour Stripe Checkout URL for Free accounts or the existing customer's Stripe billing portal. This always asks the human to confirm the same plan first; a cancellation creates nothing.

NameTypeReqDescription
planstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the goldprice.dev MCP server?

goldprice.dev is an MCP server listed in the public MCP registry as dev.goldprice/mcp. Gold/silver/copper spot & futures, per-country dealer prices, options-implied probability surface. This page covers its hosted endpoint (https://api.goldprice.dev/v1/mcp/).

Is the goldprice.dev MCP server safe to use?

goldprice.dev scores 75 out of 100 on VerifyMCP. 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 goldprice.dev MCP server expose?

goldprice.dev exposes 9 tools: start_checkout, get_spot_price, list_commodities, get_metadata, get_carat, and 4 more. Their descriptions and schemas cost roughly 839 tokens of context every time the server is loaded.

Does the goldprice.dev MCP server require authentication?

No. We connected to goldprice.dev without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the goldprice.dev MCP server still maintained?

goldprice.dev is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.