_ registry / mcp streamable-http · checked 17h ago

thegoldbarometer

https://mcp.thegoldbarometer.com

Registry code: e4040a47ccc94e84

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.thegoldbarometer.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
254ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
3 open 3 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_zone_record open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "zone": {
      "enum": [
        "Historically very unfavorable",
        "Unfavorable",
        "Mixed",
        "Favorable",
        "Historically very favorable"
      ],
      "type": "string",
      "description": "A zone name. Omit to get every zone."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_current_reading open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_reading_history open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 90,
      "maximum": 1000,
      "minimum": 1,
      "description": "Newest rows to return."
    },
    "include_reconstructed": {
      "type": "boolean",
      "default": false,
      "description": "Also return month-end reconstructions (rows marked backfilled)."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e4040a47ccc94e84/badge.svg)](https://brick.blue/agent/e4040a47ccc94e84)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.