StackerScan
REMOTE · WWW.STACKERSCAN.COM
Five read-only tools: spot prices, observed premiums, price history, Goldback rate, and currencies.
Available components
Last scanned (13 hours ago)
Scores higher than 90% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 845 tokens (~140/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
- 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 7 Nov 26 −7
- Authorization: pass → partial ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 641 → 845 ▼ functional
- New tool “get_how_to_use” functional
- 6 Nov 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Oct 26 0
- Stability: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_observed_premiums” rewrote its description, which is the text the model reads security
- Tool “get_price_history” rewrote its description, which is the text the model reads security
- Tool “list_supported_currencies” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_price_history” added a required parameter “metal”, so existing callers break ▼ functional
- Server version: 1.4.0 → 1.5.2 functional
- “get_price_history” added an optional parameter “base” cosmetic
- “get_price_history” added an optional parameter “cursor” cosmetic
- “get_price_history” added an optional parameter “days” cosmetic
- “get_price_history” added an optional parameter “format” cosmetic
- “get_price_history” added an optional parameter “limit” cosmetic
- 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
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 12 Sept 26 0
- Tool “get_observed_premiums” rewrote its description, which is the text the model reads security
- 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
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 7 Nov 2026 · Probed https://www.stackerscan.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.stackerscan.com | CN=YR1,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | RSA 2048 | SHA256-RSA | 5facda231886bfd0be8abf2f3d2e7b9b898 |
| SANs: www.stackerscan.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.stackerscan.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| stackerscan.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| permissions-policy | identity-credentials-get=* |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.stackerscan.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.stackerscan.com/mcp | HTTPS enforced | 308 | https://www.stackerscan.com/mcp |
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 →
get_goldback_rate Goldback exchange rate ~65
The latest Goldback premium multiple over its gold content, and the exchange rate that follows from it.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | A currency code from the live catalog at /api/currencies (ISO 4217 fiat plus BTC and the metal codes). Defaults to USD. |
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | Resolved uppercase currency code. |
| goldContentTroyOz | number | yes | Fine-gold content of one Goldback note. |
| goldSpotPerTroyOz | number | yes | Underlying gold spot price per troy ounce in the base currency. |
| premiumMultiple | number | yes | Multiple applied to the note's contained-gold spot value. |
| rateDate | string | yes | Effective date of the premium multiple. |
| ratePerGoldback | number | yes | Price of one Goldback: goldSpotPerTroyOz × goldContentTroyOz × premiumMultiple. |
| spotAsOf | string | yes | UTC update instant of the gold spot input. |
No examples provided.
get_how_to_use How to Use guide ~189
StackerScan's How to Use guide in any app language: its table of contents, or one section as markdown quoting the app's own button and field labels. Sections: createAccount (Your Account), stackSettings (Stack Settings), addItems (Adding Items to Your Stack), editItems (Editing, Selling and Deleting Items), addPhotos (Adding Photos to Your Items), managePortfolio (Understanding Your Portfolio Overview), worthToday (How Items Are Valued), dataFields (Understanding Your Item Data Fields), useTags (How to Use Tags), useCredits (Using Credits), trackPrices (Tracking Metal Prices), premiums (Checking Premiums), stackChat (Asking About Your Stack).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | App language, for the labels a person sees in it. Defaults to en. |
| section | string | – | A section id. Omit for the table of contents. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | – | – |
| section | string | – | – |
| sections | array | – | – |
| title | string | – | – |
No examples provided.
get_observed_premiums Observed premiums over spot ~114
Rolling fine-metal-weighted median asking premiums for silver, gold, platinum, palladium, copper, nickel and Goldback, observed from marketplace listings.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque continuation token returned by the same tool with exactly the same filters. |
| limit | integer | – | Product page size. Without a query, pages browse the most-listed products. |
| metal | string | yes | Which metal's observed premiums to return. |
| query | string | – | Case-insensitive product label/canonical-key search. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | UTC latest observation instant. |
| categories | array | yes | – |
| metal | string | yes | – |
| minimumListings | integer | yes | – |
| nextCursor | – | yes | – |
| overall | – | yes | – |
| productOrder | string | yes | How product rows were selected: search (query match, catalog order) or listing_count (browse, most-listed first). Empty products means no data. |
| productQuery | – | yes | – |
| products | array | yes | – |
| sourceUrl | string | yes | – |
| windowDays | integer | yes | – |
No examples provided.
get_price_history Historical price series ~141
Daily historical series for charting — one metal or the Goldback.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | A currency code from the live catalog at /api/currencies (ISO 4217 fiat plus BTC and the metal codes). Defaults to USD. |
| cursor | string | – | Opaque continuation token returned by the same tool with exactly the same filters. |
| days | integer | – | How many trailing days of history to return. |
| format | string | – | ohlc returns open/high/low/close rows; line returns closes. |
| limit | integer | – | – |
| metal | string | yes | The metal (or Goldback) whose history to return. |
Structured output declared, but exposes no named fields.
No examples provided.
get_spot_prices Spot metal prices ~148
Current and previous-session spot prices for gold, silver, platinum, palladium, copper and nickel, in any supported currency and per troy ounce or gram.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | A currency code from the live catalog at /api/currencies (ISO 4217 fiat plus BTC and the metal codes). Defaults to USD. |
| metals | array | – | Metal symbols to include (xau gold, xag silver, xpt platinum, xpd palladium, xcu copper, ni nickel). Omit for all six; Goldback is not a spot metal. |
| unit | string | – | Price per troy ounce or per gram. Defaults to troy_oz. |
| Name | Type | Req | Description |
|---|---|---|---|
| asOf | string | yes | UTC source update instant. |
| base | string | yes | Resolved uppercase currency code. |
| date | string | yes | Market or session date. |
| metals | object | yes | Requested spot symbols only; Goldback is not a spot metal. |
| unit | string | yes | Shared price denominator for every returned metal. |
No examples provided.
list_supported_currencies Supported currency catalog ~80
The live list of codes every `currency`/`base` parameter accepts — ISO 4217 fiat plus the metal codes.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque continuation token returned by the same tool with exactly the same filters. |
| limit | integer | – | – |
| query | string | – | Case-insensitive substring match against code or name. |
| Name | Type | Req | Description |
|---|---|---|---|
| currencies | array | yes | – |
| nextCursor | – | yes | – |
| query | – | yes | – |
No examples provided.
How do I install the StackerScan MCP server?
StackerScan is a hosted endpoint at https://www.stackerscan.com/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 · www.stackerscan.com
claude mcp add --transport http com-stackerscan-stackerscan 'https://www.stackerscan.com/mcp'
What is the StackerScan MCP server?
StackerScan is an MCP server listed in the public MCP registry as com.stackerscan/stackerscan. Five read-only tools: spot prices, observed premiums, price history, Goldback rate, and currencies. This page covers its hosted endpoint (https://www.stackerscan.com/mcp).
Is the StackerScan MCP server safe to use?
StackerScan scores 85 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 StackerScan MCP server expose?
StackerScan exposes 6 tools: get_spot_prices, get_observed_premiums, get_price_history, get_goldback_rate, list_supported_currencies, get_how_to_use. Their descriptions and schemas cost roughly 737 tokens of context every time the server is loaded.
Does the StackerScan MCP server require authentication?
No. We connected to StackerScan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the StackerScan MCP server still maintained?
StackerScan is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the StackerScan MCP server?
VerifyMCP ran 13 checks on StackerScan, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.