getticker: the Ticker door

io.github.alloolooPublished by GitHub account allooloov0.1.0Updated Nov 5, 2026

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

VerifiedStreamable HTTPWeb executableFinanceKnowledge & Memory

Overview

AI-generated overview

Remote MCP door that resolves a ticker, ISIN or LEI to its issuer, listing and status, with signed, receipted answers.

What you can do
  • Look up the issuer behind a ticker and exchange, or behind an ISIN or LEI, returning the issuer, ISIN, LEI, listing and status
  • Resolve a listed company by ticker, ISIN or LEI, with the apex naming the owning node and forwarding to that node's regional door
  • List the market nodes on the roster, showing which are live, their regional doors and Agent Cards
  • Each returned value carries its source page and read date, is signed by the node of the listing's market and receipted; values the record does not carry are marked not_on_record
When to use it
Useful when an assistant needs to identify the legal issuer behind a security identifier, confirm where a company is listed and its status, or check which market nodes are available before a lookup. It is a read-only index and router, not a source of prices or filings.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared. No authentication is declared. Network access to the endpoint is required.
Before you install
Reads are described as free, but an x402 payment offer exists and is triggered when a request asks for it (x402-pay: 1), so payment-related requests should be deliberate. The server is an index and router that forwards lookups to regional market nodes and receipts them at a third-party receipt service, so queries and their answers pass through those parties.

Installation

In SourceWeft

  1. Open getticker: the Ticker door in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.allooloo%2Fgetticker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "getticker-the-ticker-door": {
      "type": "http",
      "url": "https://mcp.getticker.ai/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

get_ticker

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.

Parametersmarketexchangeidentifierrequired

resolve_issuer

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.

Parametersidentifierrequired

list_nodes

List market nodes

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

Takes no parameters.

Version history

1
  1. v0.1.0LatestNov 5, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.