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.

Proof of Stock

REMOTE · PROOFOFSTOCK.XYZ

RWA: is this stock token the issuer's? Base and Robinhood Chain, with a list hash to recheck.

Available components

+3 this week 74 Trust /100

Last scanned (14 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 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
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1948 tokens (~278/item across 7 items; 7 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

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.

  • 20 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.7.0 → 0.8.0 functional
    • “stock_passport” reworded the description of “hours” cosmetic
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 0
    • Server version: 0.6.0 → 0.7.0 functional
    • Server version: 0.5.1 → 0.6.0 functional
  • 14 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “recent_impostors” rewrote its description, which is the text the model reads security
    • Schema quality: 1619 → 1932 ▼ functional
    • New tool “verify_anchor” functional
    • “stock_passport” reworded the description of “hours” cosmetic
  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 70

    First indexed and scored.

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 21 Nov 2026 · Probed https://proofofstock.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=proofofstock.xyz CN=YE2,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 6d8c674fda7b5b92ff9865e6549bd8d5072
SANs: *.proofofstock.xyz, proofofstock.xyz
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of proofofstock.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
proofofstock.xyz. 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=31536000
content-security-policy default-src 'none'; script-src 'self'; style-src 'self' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data:; connect-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://proofofstock.xyz/mcp Verified 200
http (plaintext) http://proofofstock.xyz/mcp HTTPS enforced 301 https://proofofstock.xyz/mcp
MCP tools · 7 exposed · ~1,676 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
compare_venues ~232

For shares listed on BOTH Base (Coinbase) and Robinhood Chain (Robinhood), matched by ISIN: per venue the on-chain price's premium over that venue's own issuer reference, the reference kind and age, the deepest pool's liquidity and the multiplier, and the gap (Robinhood premium minus Base premium) when both are current. Raw prices are never compared: multipliers and references differ (Coinbase NAV vs Robinhood bid/ask), so a gap is not a price difference or an arbitrage. Name a share by isin or by ticker (NVDA, or NVDAc); with neither, the 20 rows with the largest gap. A missing premium carries its reason; a reading older than 30 min is flagged stale and gets no gap. Facts, not advice.

NameTypeReqDescription
isinstring–the share's ISIN, e.g. US67066G1040 for NVIDIA
symbolstring–the ticker, plain or as the issuer writes it (NVDA or NVDAc); give isin or symbol, or neither for the 20 largest gaps

No output schema declared.

No examples provided.

find_stock_token ~190

Find issuer-listed tokenized stocks on a chain by ticker, company name or ISIN. Returns the official contract addresses. An empty result says only that the issuer lists no such token, nothing about impostors. Two chains: base (Coinbase's tokens, symbols end in "c", e.g. NVDAc) and robinhood (Robinhood's, e.g. NVDA). When the user names no chain, call it for both. Facts with their time and source, not advice: https://proofofstock.xyz/docs/legal.md

NameTypeReqDescription
chainstringyeswhich chain and issuer list to check: base (Coinbase's list) or robinhood (Robinhood Chain, Robinhood's list)
querystringyesa ticker (NVDA or NVDAc), a company name (Tesla) or an ISIN (US67066G1040)

No output schema declared.

No examples provided.

list_stock_tokens ~196

List every token in a chain's issuer registry: symbol, name, contract address, ISIN, multiplier, whether it is minted on the chain and whether the issuer publishes a reference price. The answer opens with the exact count (also the `count` field); quote that number, do not estimate it from the list. On Base many listed tokens are not minted yet and do not trade (`minted`). Two chains: base (Coinbase's tokens, symbols end in "c", e.g. NVDAc) and robinhood (Robinhood's, e.g. NVDA). When the user names no chain, call it for both. Facts with their time and source, not advice: https://proofofstock.xyz/docs/legal.md

NameTypeReqDescription
chainstringyeswhich chain and issuer list to check: base (Coinbase's list) or robinhood (Robinhood Chain, Robinhood's list)

No output schema declared.

No examples provided.

recent_impostors ~197

Tokens on a chain FIRST FLAGGED IN THE LAST 7 DAYS whose symbol or name copies an issuer-listed stock token while their contract is not in that registry, newest first (at most 50), optionally since an ISO time within that window. This is a window, not the whole list: the answer carries `window_days`, `count` for the window and `listed_total` for every look-alike on the list. Each names what it imitates and the listed address. A claim with evidence, not a verdict.

NameTypeReqDescription
chainstringyeswhich chain and issuer list to check: base (Coinbase's list) or robinhood (Robinhood Chain, Robinhood's list)
sincestring–only look-alikes first flagged at or after this ISO 8601 time, e.g. 2026-11-12T00:00:00Z; omit for the newest 50

No output schema declared.

No examples provided.

stock_passport ~496

Passport of one token address: whether it is in the issuer registry (and, if not, which listed stock its name imitates); the issuer reference price and its age; the latest DEX price and its premium over the reference; the premium series split by US market session; and every gap named. Readings are recorded every 15 minutes (latest.cadence_s), so "latest" is a recorded reading, not a live quote: see latest.age_s. premium compares the latest on-chain price with the issuer reference, whose own age is reference.age_s; when the two are far apart in time, latest.premium_at_reference_time gives the premium of one moment. sources names every source and the pool rule. Every answer opens with one plain sentence; quote it. In the JSON, premium and spread are FRACTIONS (0.01 = 1%; premium > 0 means the on-chain price is above the issuer's), *_age_s and age_s are seconds before generated_at, prices are USD per token. A token is worth `multiplier` shares, and the issuer's reference is already per token. reference.kind: nav_total_return = Coinbase's NAV, token_bid_ask_mid = the mid of Robinhood's token bid/ask. notes are codes for every gap (e.g. reading_stale = our last reading is over 30 min old, pools_capped = the pool count is a minimum). Two chains: base (Coinbase's tokens, symbols end in "c", e.g. NVDAc) and robinhood (Robinhood's, e.g. NVDA). When the user names no chain, call it for both. Facts with their time and source, not advice: https://proofofstock.xyz/docs/legal.md

NameTypeReqDescription
addressstringyesthe token contract address to check, 0x and 40 hex digits; any token, listed or not
chainstringyeswhich chain and issuer list to check: base (Coinbase's list) or robinhood (Robinhood Chain, Robinhood's list)
hoursnumber–how many hours of premium history to summarise, 1 to 24 (this server shows at most 24)
include_seriesboolean–also return series_points, the raw premium time series (large); the session medians in `series` are always there

No output schema declared.

No examples provided.

verify_anchor ~167

Proof that our record of one day has not been changed since: the SHA-256 of that day's manifest of data files, the state of its OpenTimestamps proof (pending, or the Bitcoin block it is in), and the transaction carrying the same hash on Base and on Robinhood Chain. Bitcoin is the root, because Base is sequenced by Coinbase and Robinhood Chain by Robinhood, the two issuers we check; the other two are mirrors, for reach. The answer gives the manifest URL, the proof files and each transaction hash, which is everything needed to check it WITHOUT us. Omit day for the newest anchored day.

NameTypeReqDescription
daystring–the UTC day to check, e.g. 2026-11-12; omit for the newest anchored day

No output schema declared.

No examples provided.

verify_stock_tokens ~198

Before buying a token that claims to be a stock, check its contract address: is it on the issuer's own registry for this chain (Base: Coinbase; robinhood: Robinhood)? Up to 50 addresses per call. listed=true is decided by the exact address alone. listed=false means "not in this issuer's registry", not "fake" (it may be another issuer's token); impostor is set only when the token copies a listed symbol or the issuer's naming, and then listed_address is the real one. If the registry cannot be read the call fails rather than answering false. Facts, not advice.

NameTypeReqDescription
addressesarrayyesthe token contract addresses to check, 1 to 50, each 0x and 40 hex digits
chainstringyeswhich chain and issuer list to check: base (Coinbase's list) or robinhood (Robinhood Chain, Robinhood's list)

No output schema declared.

No examples provided.

Install

How do I install the Proof of Stock MCP server?

Proof of Stock is a hosted endpoint at https://proofofstock.xyz/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 · proofofstock.xyz

# add to Claude Code
claude mcp add --transport http xyz-proofofstock-proof-of-stock 'https://proofofstock.xyz/mcp'
Common questions

What is the Proof of Stock MCP server?

Proof of Stock is an MCP server listed in the public MCP registry as xyz.proofofstock/proof-of-stock. RWA: is this stock token the issuer's? Base and Robinhood Chain, with a list hash to recheck. This page covers its hosted endpoint (https://proofofstock.xyz/mcp).

Is the Proof of Stock MCP server safe to use?

Proof of Stock scores 74 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 Proof of Stock MCP server expose?

Proof of Stock exposes 7 tools: find_stock_token, list_stock_tokens, stock_passport, verify_stock_tokens, recent_impostors, and 2 more. Their descriptions and schemas cost roughly 1,676 tokens of context every time the server is loaded.

Does the Proof of Stock MCP server require authentication?

No. We connected to Proof of Stock without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Proof of Stock MCP server still maintained?

Proof of Stock is still listed as active in the MCP registry. We last reached this channel on 21 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 Proof of Stock MCP server?

VerifyMCP ran 13 checks on Proof of Stock, 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.