Stocks On Chain
REMOTE · STOCKSONCHAIN.IO
Read-only tokenized stock data: issuers, chains, contract addresses and corporate actions.
Available components
Last scanned (8 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1339 tokens (~167/item across 8 items; 8 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 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 123 → 158 ▼ functional
- New tool “report_gap” 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
- 14 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_contract” rewrote its description, which is the text the model reads security
- Tool “list_issuers” rewrote its description, which is the text the model reads security
- Tool “search_stocks” rewrote its description, which is the text the model reads security
- 29 Aug 26 0
- Stability: 0.97 → pass 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
- 20 Aug 26 0
- Tool “list_issuers” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ 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 5 Nov 2026 · Probed https://stocksonchain.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stocksonchain.io | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3b1c0c2018ed62b913f01473e2610d0a |
| SANs: stocksonchain.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of stocksonchain.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| stocksonchain.io. | present | 2371 | 13 | Verified |
| stocksonchain.io. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stocksonchain.io/mcp | Verified | 200 | |
| http (plaintext) | http://stocksonchain.io/mcp | HTTPS enforced | 301 | https://stocksonchain.io/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_contract Look up a contract address ~240
What this site holds about one address, in two independent halves. `listings` says what the token IS - the stock, its company, the issuer and the chain - and is present whenever the address is a listing we track. `matches` says what the CODE at the address is: its runtime bytecode hash, the implementation behind it if it is a proxy, and how many other addresses we track run byte-identical code; it is present only where we have read the code. The code half is reproducible: fetch eth_getCode and take its keccak256 and you get the same hash. Either half can be empty and both can be present; an address we hold nothing about returns found: false, which is an answer rather than an error. This never says an address is safe, genuine or correct, and there is no field that could: check it against the issuer before you act on it.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The contract address, in any case. |
| chain | string | – | Chain slug, for example ethereum or robinhood-chain. Optional. Omit it to find the address on every chain we hold it. |
No output schema declared.
No examples provided.
get_manifest Get the agent tier terms ~52
What this service offers a machine reader: the free keyless endpoints, the bulk dataset and its price if the paid tier is live, and the licence. No human reader is ever charged or asked to connect a wallet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stock Get one tokenized stock ~93
Everything known about one stock: every instrument (one per issuer, with the mechanics union describing how it handles corporate actions), every listing under it (chain, contract address, supply, price), and the events recorded against it. Report instruments as the options; listings are addresses. Read mechanics.kind before reaching for any field inside mechanics.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Ticker or slug, for example NVDA or nvda. |
No output schema declared.
No examples provided.
list_chains List chains ~40
Every chain carrying tokenized stocks, with its explorer, and the matrix of which issuer has listed what where. Registry order, which is not a ranking.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_events List corporate actions ~91
The corporate-action tape: splits, distributions and multiplier changes read from chain state, each with a transaction hash. Newest first by the time the event took effect, which is chronology and not a ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many events to return. Default 50, maximum 500. |
| since | string | – | ISO 8601 date. Only return events effective on or after this date. |
No output schema declared.
No examples provided.
list_issuers List issuers ~85
Every issuer whose tokens are tracked, in registry order, with the legal wrapper it uses, the chains it issues on, and a link to where that issuer publishes its own rule on who may buy. The rule itself is deliberately not included: it can change without this site noticing, so answer eligibility questions by sending the caller to eligibility.sourceUrl rather than by stating a rule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report_gap Report something this site does not have ~356
Tell us you wanted something and did not get it: a stock we do not track, a chain a stock is not on, a field no endpoint carries, a tool that does not exist, a figure you believe is wrong, or a path that failed. Call this when another tool has just answered with a miss - the answer names the kind to send. THERE IS NO FREE-TEXT FIELD AND THERE WILL NOT BE ONE: a report is an enumerated kind plus a short subject, because the counts are what is useful and prose from an anonymous caller is a prompt-injection surface pointed at the people who read it. Nothing about you is recorded - no address, no header, no identifier - so a report cannot be joined to a caller and there is no reply. The report is counted in aggregate and returned to you with a prefilled link a human can open to track it. Reporting costs nothing and is never required.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | What was missing. One of: missing_stock (A stock this site does not track at all.) missing_listing (A stock we track, but not on the chain the caller wanted.) missing_field (A field no endpoint carri… |
| subject | string | yes | What it was about - a ticker, a field name, a tool name or a path. Letters, digits, dot, slash, hyphen and underscore, up to 64 characters. Not a sentence: there is no free-text field. A wallet or co… |
No output schema declared.
No examples provided.
search_stocks Search tokenized stocks ~88
Find tokenized stocks by ticker or company name. Returns every match with its issuers and chains, alphabetical by ticker. If a ticker is a real stock but has not been tokenized, this reports that too, which is a correct answer rather than an empty result.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A ticker (NVDA) or part of a company name (Nvidia). Case insensitive. |
No output schema declared.
No examples provided.
How do I install the Stocks On Chain MCP server?
Stocks On Chain is a hosted endpoint at https://stocksonchain.io/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 · stocksonchain.io
claude mcp add --transport http io-stocksonchain-stocks-on-chain 'https://stocksonchain.io/mcp'
What is the Stocks On Chain MCP server?
Stocks On Chain is an MCP server listed in the public MCP registry as io.stocksonchain/stocks-on-chain. Read-only tokenized stock data: issuers, chains, contract addresses and corporate actions. This page covers its hosted endpoint (https://stocksonchain.io/mcp).
Is the Stocks On Chain MCP server safe to use?
Stocks On Chain scores 79 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 Stocks On Chain MCP server expose?
Stocks On Chain exposes 8 tools: search_stocks, get_stock, list_issuers, list_chains, list_events, and 3 more. Their descriptions and schemas cost roughly 1,045 tokens of context every time the server is loaded.
Does the Stocks On Chain MCP server require authentication?
No. We connected to Stocks On Chain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Stocks On Chain MCP server still maintained?
Stocks On Chain is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.