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.kingleosgold/troystack

REMOTE · API.TROYSTACK.AI

Precious metals AI analyst with 12 tools — prices, portfolio, chat, receipts, and more.

Available components

0 this week 81 Trust /100

Last scanned (22 hours ago)

Scores higher than 84% of remote servers

Unreachable for 1 day in a row. Last reached 3 Nov 2026.

Category Finance and Payments

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 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
  • 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
  • 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
    • Stability: 0.97 → pass security
  • 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
  • 31 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
  • 30 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
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 4 Nov 2026 · Probed https://api.troystack.ai/mcp

TLS unreached
DNSSEC insecure

Validation of api.troystack.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
troystack.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.troystack.ai/mcp Unreachable
http (plaintext) http://api.troystack.ai/mcp HTTPS enforced
MCP tools · 12 exposed · ~811 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
add_holding ~116

Add a precious metals purchase to your portfolio

NameTypeReqDescription
api_keystringyesTroyStack API key (required)
metalstringyesMetal type
purchase_datestring–Purchase date YYYY-MM-DD (default: today)
purchase_pricenumberyesPrice per piece in USD
quantityintegeryesNumber of pieces
typestring–Product name (e.g. "2024 American Silver Eagle")
weight_oznumberyesWeight per piece in troy ounces

No output schema declared.

No examples provided.

chat_with_troy ~69

Ask Troy anything about precious metals, markets, your stack. Provide api_key for personalized portfolio-aware answers, or omit for general market analysis.

NameTypeReqDescription
api_keystring–TroyStack API key for portfolio-aware responses (optional)
messagestringyesYour question or message for Troy

No output schema declared.

No examples provided.

get_analytics ~42

Cost basis, average cost per oz, break-even price, unrealized P/L per metal

NameTypeReqDescription
api_keystringyesTroyStack API key (required)

No output schema declared.

No examples provided.

get_daily_brief ~50

Troy's daily market brief. Provide api_key for personalized brief, or omit for the latest Stack Signal market synthesis.

NameTypeReqDescription
api_keystring–TroyStack API key for personalized brief (optional)

No output schema declared.

No examples provided.

get_junk_silver ~170

Calculates silver melt value for pre-1965 US coinage

NameTypeReqDescription
dimesinteger–Roosevelt/Mercury dime count (0.07234 oz Ag each)
dollarsinteger–Morgan/Peace dollar count (0.77344 oz Ag each)
half_dollarsinteger–Walking Liberty/Franklin/1964 Kennedy half count (0.36169 oz Ag each)
kennedy_40integer–Kennedy 1965-1970 40% silver halves (0.14792 oz Ag each)
quartersinteger–Washington quarter count (0.18084 oz Ag each)
war_nickelsinteger–Jefferson 1942-1945 war nickel count (0.05626 oz Ag each)

No output schema declared.

No examples provided.

get_portfolio ~47

Returns your precious metals portfolio: total value, cost basis, gain/loss, per-metal breakdown, and individual holdings

NameTypeReqDescription
api_keystringyesTroyStack API key (required)

No output schema declared.

No examples provided.

get_price_history ~49

Historical spot price data for a precious metal over a time range

NameTypeReqDescription
metalstringyesThe metal to fetch history for
rangestring–Time range (default 1Y)

No output schema declared.

No examples provided.

get_speculation ~71

Calculates price multipliers comparing current spot to hypothetical target prices

NameTypeReqDescription
goldnumber–Target gold price per oz
palladiumnumber–Target palladium price per oz
platinumnumber–Target platinum price per oz
silvernumber–Target silver price per oz

No output schema declared.

No examples provided.

get_spot_prices ~29

Returns current spot prices for gold, silver, platinum, and palladium with daily change percentages

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_stack_signal ~64

Returns Stack Signal — TroyStack's curated precious metals market intelligence with Troy's commentary

NameTypeReqDescription
categorystring–Optional category filter
limitinteger–Max articles to return (default 20)
offsetinteger–Pagination offset (default 0)

No output schema declared.

No examples provided.

get_vault_watch ~51

Returns COMEX warehouse inventory: registered, eligible, combined ounces, daily changes, open interest, oversubscribed ratio

NameTypeReqDescription
metalstring–Optional metal filter; returns all 4 if omitted

No output schema declared.

No examples provided.

scan_receipt ~53

Extract precious metals purchase data from a receipt image using AI vision

NameTypeReqDescription
api_keystringyesTroyStack API key (required)
image_base64stringyesBase64-encoded receipt image (JPEG)

No output schema declared.

No examples provided.

Install

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

io.github.kingleosgold/troystack is a hosted endpoint at https://api.troystack.ai/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.troystack.ai

# add to Claude Code
claude mcp add --transport http kingleosgold-troystack 'https://api.troystack.ai/mcp'
Common questions

What is the io.github.kingleosgold/troystack MCP server?

io.github.kingleosgold/troystack is an MCP server listed in the public MCP registry as io.github.kingleosgold/troystack. Precious metals AI analyst with 12 tools, prices, portfolio, chat, receipts, and more. This page covers its hosted endpoint (https://api.troystack.ai/mcp).

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

io.github.kingleosgold/troystack scores 81 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 io.github.kingleosgold/troystack MCP server expose?

io.github.kingleosgold/troystack exposes 12 tools: get_spot_prices, get_price_history, get_stack_signal, get_vault_watch, get_junk_silver, and 7 more. Their descriptions and schemas cost roughly 811 tokens of context every time the server is loaded.

Does the io.github.kingleosgold/troystack MCP server require authentication?

Its publisher declares no required credentials for io.github.kingleosgold/troystack. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the io.github.kingleosgold/troystack MCP server still maintained?

io.github.kingleosgold/troystack is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.