mcp-registry/dev.goldprice/mcp · v3.2.4
As of 2026-10-18 01:16 UTC, the Goldprice MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 1 minutes.
Gold/silver/copper spot & futures, per-country dealer prices, options-implied probability surface.
Claude Code
claude mcp add --transport http goldprice-mcp-server https://api.goldprice.dev/v1/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"goldprice-mcp-server": {
"type": "http",
"url": "https://api.goldprice.dev/v1/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
13 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~2,024 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
1 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
In the last 30 days: 0 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.goldprice%2Fmcp/fixes
{
"name": "start_checkout",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"plan"
],
"properties": {
"plan": {
"enum": [
"basic_2026",
"plus_2026",
"pro_2026"
],
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.goldprice/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.goldprice/mcp"}) over MCP.
get_historical ~246 tokensget_physical_price ~187 tokensget_carat ~156 tokensget_spot_price ~149 tokensstart_checkout ~130 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.goldprice%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.goldprice%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.goldprice%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.goldprice%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fdev.goldprice%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3e26d2080ba51ba3…, first seen 2026-10-17, included at leaf 14167 of 19,485. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable knowledge servers · most reliable search servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 01:16 UTC, the Goldprice MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 35 outages in 90 days, with a median recovery of 1 minutes.
Goldprice MCP server advertises 9 tools, including get_carat, get_forward_view, get_historical, get_metadata, get_physical_price.
Point your MCP client at this streamable-http endpoint: https://api.goldprice.dev/v1/mcp/
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.