# getticker: the Ticker door (remote · mcp.getticker.ai)

The issuer behind a ticker: ISIN, LEI, listing and status, from the record: signed and receipted.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.getticker.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/allooloo-getticker/mcp.md), [page](https://verifymcp.io/servers/allooloo-getticker/mcp)

## Channel facts

- Endpoint: `https://mcp.getticker.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 615 tokens (~205/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the getticker: the Ticker door MCP server?

getticker: the Ticker door is a hosted endpoint at https://mcp.getticker.ai/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.

### Claude

```bash
claude mcp add --transport http allooloo-getticker 'https://mcp.getticker.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "allooloo-getticker": {
      "url": "https://mcp.getticker.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "allooloo-getticker": {
      "type": "http",
      "url": "https://mcp.getticker.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.allooloo-getticker]
url = "https://mcp.getticker.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "allooloo-getticker": {
      "type": "remote",
      "url": "https://mcp.getticker.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add allooloo-getticker --url 'https://mcp.getticker.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  allooloo-getticker:
    url: "https://mcp.getticker.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "allooloo-getticker": {
      "Transport": "http",
      "Url": "https://mcp.getticker.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add allooloo-getticker -t streamable-http -u 'https://mcp.getticker.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "allooloo-getticker": {
      "type": "http",
      "url": "https://mcp.getticker.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66)

First indexed and scored.

## MCP tools (3)

### `get_ticker` (~199 tokens)

Get the issuer behind a ticker

get_ticker is the issuer behind a ticker: a ticker and its exchange, or an ISIN or LEI, returns the issuer, its ISIN, its LEI, its listing and its status — every value with its source page and read date, signed by the node of the listing's market and receipted. Served from the record as read; a value the market's record does not carry says not_on_record. Typed errors: unknown_issuer, ambiguous, not_on_record (per field, per market), invalid_request. Door: https://mcp.getticker.ai/mcp (routes to the owning node); every node door answers it for its own market.

Input parameters:

- `exchange` (string): Optional exchange for a ticker (NASDAQ, LSE, XETRA, TSX, …).
- `identifier` (string, required): Ticker, ISIN or LEI.
- `market` (string): Optional two-letter market code.

### `resolve_issuer` (~109 tokens)

Resolve issuer

Find a listed company by ticker, ISIN or LEI: the apex names the owning node and forwards to that node's regional door for the record summary.

Input parameters:

- `identifier` (string, required): Ticker with or without exchange (SHOP, TSX:SHOP, SHEL.L, BHP.AX, D05.SI, NESN.SW, SAP.DE, 7203.T, 005930.KS), ISIN, LEI, an exact legal name or a sourced alias.

### `list_nodes` (~33 tokens)

List market nodes

Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/allooloo-getticker/mcp#diagnostics

## Score history

- 2026-11-05: 66

## Common questions

### What is the getticker: the Ticker door MCP server?

getticker: the Ticker door is an MCP server listed in the public MCP registry as io.github.allooloo/getticker. The issuer behind a ticker: ISIN, LEI, listing and status, from the record: signed and receipted. This page covers its hosted endpoint (https://mcp.getticker.ai/mcp).

### Is the getticker: the Ticker door MCP server safe to use?

getticker: the Ticker door scores 66 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 getticker: the Ticker door MCP server expose?

getticker: the Ticker door exposes 3 tools: get_ticker, resolve_issuer, list_nodes. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.

### Does the getticker: the Ticker door MCP server require authentication?

No. We connected to getticker: the Ticker door without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the getticker: the Ticker door MCP server still maintained?

getticker: the Ticker door 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.

### What did VerifyMCP test on the getticker: the Ticker door MCP server?

VerifyMCP ran 11 checks on getticker: the Ticker door, covering TLS certificate, Authorization, HSTS header, DNSSEC and 7 more. 2 items could not be completed, a gap on our side rather than a finding about getticker: the Ticker door: HTTPS and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.

## Links

- Remote endpoint: https://mcp.getticker.ai/mcp
- Repository: https://github.com/allooloo/cm-kg
- Website: https://getticker.ai/
- Changelog RSS feed: https://verifymcp.io/servers/allooloo-getticker/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/allooloo-getticker/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/allooloo-getticker/mcp.json
- HTML version of this page: https://verifymcp.io/servers/allooloo-getticker/mcp