Stocks On Chain

Read-only tokenized stock data: issuers, chains, contract addresses and corporate actions.

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
72%
Qualität der Benennung
98%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~1,277Tokens (Tool-Definitionen)
~786 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (1.00% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "stocks-on-chain": {
      "url": "https://stocksonchain.io/mcp"
    }
  }
}

Remote-Endpunkte

https://stocksonchain.io/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (8)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢search_stocks(query)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "A ticker (NVDA) or part of a company name (Nvidia). Case insensitive."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
🟢get_stock(ticker)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "ticker": {
      "type": "string",
      "description": "Ticker or slug, for example NVDA or nvda."
    }
  },
  "required": [
    "ticker"
  ],
  "additionalProperties": false
}
🟡list_issuers

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_chains

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_events(limit, since)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "How many events to return. Default 50, maximum 500.",
      "minimum": 1,
      "maximum": 500
    },
    "since": {
      "type": "string",
      "description": "ISO 8601 date. Only return events effective on or after this date."
    }
  },
  "additionalProperties": false
}
🟢get_contract(address, chain)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "The contract address, in any case."
    },
    "chain": {
      "type": "string",
      "description": "Chain slug, for example ethereum or robinhood-chain. Optional. Omit it to find the address on every chain we hold it."
    }
  },
  "required": [
    "address"
  ],
  "additionalProperties": false
}
🟢get_manifest

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢report_gap(kind, subject)

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.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "kind": {
      "type": "string",
      "description": "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 carries.) missing_tool (An MCP tool that does not exist.) wrong_figure (A published figure the caller believes is wrong.) broken_endpoint (A path that failed or answered in an unusable shape.)",
      "enum": [
        "missing_stock",
        "missing_listing",
        "missing_field",
        "missing_tool",
        "wrong_figure",
        "broken_endpoint"
      ]
    },
    "subject": {
      "type": "string",
      "description": "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 contract address is refused - send the ticker or the path instead."
    }
  },
  "required": [
    "kind",
    "subject"
  ],
  "additionalProperties": false
}

Empfohlene Prompts

search_research
Search for information about [topic] using Stocks On Chain
Erwartete Tools: search_stocks
find_specific
Find [specific item] using Stocks On Chain
Erwartete Tools: search_stocks
retrieve_data
Get details about [item] from Stocks On Chain
Erwartete Tools: get_stock
fetch_info
Fetch [information type] using Stocks On Chain
Erwartete Tools: get_stock
list_items
List all [items] available in Stocks On Chain
Erwartete Tools: list_issuers

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet8 Tools
verifiziertVersion nicht aufgezeichnet7 Tools
verifiziertVersion nicht aufgezeichnet7 Tools