Stocks On Chain

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
69%
Calidad de los nombres
100%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~827Tokens (definiciones de herramientas)
~498 BTamaño de respuesta típico
Impacto moderado en la atención (0.65% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

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

Puntos de conexión remotos

https://stocksonchain.io/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (7)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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: the name and category our registry records and who told us, plus what the code at that address actually 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. The code half is reproducible: fetch eth_getCode and take its keccak256 and you get the same hash. An address that is a token listing but not in the contract registry returns the listing (stock, issuer, chain) with no code record. 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.

Esquema de entrada

{
  "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.

Esquema de entrada

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

Prompts recomendados

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

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada7 herramientas
verificadoversión no registrada7 herramientas