Ticker Symbols

Overview

Ticker Symbols is built from the listings of the US and 18 international primary exchanges, the major cryptocurrencies and the most traded futures contracts, refreshed daily. Every equity listing is confirmed against OpenFIGI, the open financial instrument identifier standard, before it is published; coins must be listed on a major exchange, and futures come from a verified contract table. The same ticker often means different things in different places - SHEL trades in London and New York, and BTC is a coin in crypto but a Bitcoin ETF on a US exchange - so every result names its market, exchange and asset class.

Live Test Ticker Symbols Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as TickerSymbols. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "TickerSymbols",
  "arguments": {
    "symbol": "SHEL"
  }
}

You do not name the tool yourself; the model picks it. Asking about SHEL in the terms this source covers is enough for it to reach for TickerSymbols on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

https://api.vervecontext.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39

{
  "status": "ok",
  "error": null,
  "data": {
    "symbol": "SHEL",
    "search": null,
    "count": 2,
    "results": [
      {
        "symbol": "SHEL",
        "name": "Shell PLC American Depositary Shares (each representing two (2) Ordinary Shares)",
        "market": "US",
        "country": "US",
        "exchange": "XNYS",
        "exchangeName": "New York Stock Exchange",
        "type": "Depositary Receipt",
        "assetClass": "equity",
        "figi": "BBG0147BN6G2",
        "compositeFigi": "BBG0147BN6G2",
        "shareClassFigi": "BBG0147BN6H1",
        "cik": "0001306965"
      },
      {
        "symbol": "SHEL",
        "name": "Shell Plc",
        "market": "GB",
        "country": "GB",
        "exchange": "XLON",
        "exchangeName": "London Stock Exchange",
        "type": "Common Stock",
        "assetClass": "equity",
        "figi": "BBG0149N4YC8",
        "compositeFigi": "BBG0149N4YB9",
        "shareClassFigi": "BBG0149N4YG4",
        "cik": null
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at count: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 1 credit each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Symbol Autocomplete

Trading and portfolio apps suggest listings as users type a company name or the first letters of a ticker.

Listing Disambiguation

Data pipelines resolve an ambiguous ticker such as SHEL or BTC to the exact market, exchange and asset class before pricing it.

Identifier Mapping

Back offices join their own ticker lists to FIGI identifiers and SEC CIK numbers for reporting and reconciliation.

Asset Classification

Watchlists and screeners label every holding as an equity, fund, cryptocurrency, commodity or financial future.

Other ways to use Ticker Symbols

Set up Ticker Symbols on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Related

More in Finance: