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.

io.github.thegoldbarometer/thegoldbarometer

NPM · THEGOLDBAROMETER-MCP · 2 COMPONENTS

Today's gold buying-conditions score (0-100), its published history, and what followed since 1971.

0 this week 80 Trust /100

Last scanned (14 hours ago)

Scores higher than 66% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 239 tokens (~79/item across 3 items; 3 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 −3
    • Stability: pass → 0.83 functional
  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 −1
    • Stability: pass → 0.97 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 21 Nov 2026 · Analysed npm/thegoldbarometer-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

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 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~239 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_current_reading ~63

Today's Gold Barometer reading: the 0-100 gold buying-conditions score, its zone, and the state of each measured part. Updated daily after the US market closes. It measures conditions. It is not advice, and it does not predict the price.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_reading_history ~90

Past Gold Barometer readings, oldest first. Daily published readings by default; set include_reconstructed to true to add month-end context rows rebuilt back to 2019. The monthly record back to 1971 lives in the public archive.

NameTypeReqDescription
include_reconstructedboolean–Also return month-end reconstructions (rows marked backfilled).
limitinteger–Newest rows to return.

No output schema declared.

No examples provided.

get_zone_record ~86

What followed months that read like a given zone, across the reconstructed record since 1971: median gold move 1 and 5 years later, before and after inflation, with the month count behind each figure. It measures conditions. It is not advice, and it does not predict the price.

NameTypeReqDescription
zonestring–A zone name. Omit to get every zone.

No output schema declared.

No examples provided.

Install

How do I install the io.github.thegoldbarometer/thegoldbarometer MCP server?

io.github.thegoldbarometer/thegoldbarometer runs locally as an npm package, launched with npx -y thegoldbarometer-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 · thegoldbarometer-mcp

# add to Claude Code
claude mcp add thegoldbarometer-thegoldbarometer -- npx -y thegoldbarometer-mcp
Common questions

What is the io.github.thegoldbarometer/thegoldbarometer MCP server?

io.github.thegoldbarometer/thegoldbarometer is an MCP server listed in the public MCP registry as io.github.thegoldbarometer/thegoldbarometer. Today's gold buying-conditions score (0-100), its published history, and what followed since 1971. This page covers its npm package (thegoldbarometer-mcp).

Is the io.github.thegoldbarometer/thegoldbarometer MCP server safe to use?

io.github.thegoldbarometer/thegoldbarometer scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.thegoldbarometer/thegoldbarometer MCP server expose?

io.github.thegoldbarometer/thegoldbarometer exposes 3 tools: get_current_reading, get_reading_history, get_zone_record. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.

Is the io.github.thegoldbarometer/thegoldbarometer MCP server still maintained?

io.github.thegoldbarometer/thegoldbarometer is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.thegoldbarometer/thegoldbarometer MCP server under?

io.github.thegoldbarometer/thegoldbarometer 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 io.github.thegoldbarometer/thegoldbarometer MCP server?

VerifyMCP ran 16 checks on io.github.thegoldbarometer/thegoldbarometer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.