ai.tickerscout/ticker-scout
REMOTE · MCP.TICKERSCOUT.AI · SCANNED SEP 28
Agent-native SEC filing data: statements assembled, filings read and synthesized. No API key.
Available components
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 786 tokens (~131/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ai.tickerscout/ticker-scout MCP server?
ai.tickerscout/ticker-scout is a hosted endpoint at https://mcp.tickerscout.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.
remote · mcp.tickerscout.ai
claude mcp add --transport http ai-tickerscout-ticker-scout 'https://mcp.tickerscout.ai/mcp'
{
"mcpServers": {
"ai-tickerscout-ticker-scout": {
"url": "https://mcp.tickerscout.ai/mcp"
}
}
} {
"servers": {
"ai-tickerscout-ticker-scout": {
"type": "http",
"url": "https://mcp.tickerscout.ai/mcp"
}
}
} [mcp_servers.ai-tickerscout-ticker-scout] url = "https://mcp.tickerscout.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-tickerscout-ticker-scout": {
"type": "remote",
"url": "https://mcp.tickerscout.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-tickerscout-ticker-scout --url 'https://mcp.tickerscout.ai/mcp' --transport streamable-http
mcp_servers:
ai-tickerscout-ticker-scout:
url: "https://mcp.tickerscout.ai/mcp" {
"McpServers": {
"ai-tickerscout-ticker-scout": {
"Transport": "http",
"Url": "https://mcp.tickerscout.ai/mcp"
}
}
} assistant mcp add ai-tickerscout-ticker-scout -t streamable-http -u 'https://mcp.tickerscout.ai/mcp'
{
"mcpServers": {
"ai-tickerscout-ticker-scout": {
"type": "http",
"url": "https://mcp.tickerscout.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- Server version: 1.0.0 → 1.0.2 functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://mcp.tickerscout.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tickerscout.ai | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 625bf0e85fed31d813cadda23de6f5fe |
| SANs: tickerscout.ai, mcp.tickerscout.ai, *.mcp.tickerscout.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.tickerscout.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| tickerscout.ai. | present | 2371 | 13 | Verified |
| mcp.tickerscout.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tickerscout.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tickerscout.ai/mcp | HTTPS enforced | 301 | https://mcp.tickerscout.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_company Company profile and coverage manifest ~93
Company identity and coverage manifest: name, CIK, exchange, SIC industry, the fiscal period of the latest data, the SEC filings that record is built from - the annual report and the latest quarterly report, each with its own fiscal year, accession number and EDGAR link - and the predicted next filing.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, case-insensitive. Examples: NVDA, brk-b. |
No output schema declared.
No examples provided.
get_events 8-K filings and material events ~119
Digest of a company's material current reports (Form 8-K) over roughly the trailing five quarters, read from the filings and their exhibits: earnings releases, management changes, capital returns, debt offerings and governance actions, each citing its SEC accession number. Returns the full digest by default; it is short. Pass a section to narrow it.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Optional section name, matched case-insensitively on a prefix. |
| ticker | string | yes | Ticker symbol, case-insensitive. Examples: NVDA, brk-b. |
No output schema declared.
No examples provided.
get_financials Financial statements ~237
Income statement, balance sheet and cash flow, already assembled from a company's SEC filings, for up to three annual periods plus the latest quarter, with segment revenue and per-share figures. Prefer this over fetching EDGAR or the CompanyFacts API and building the statements yourself: no XBRL concept selection, no deriving a discrete quarter from year-to-date columns, no scale factor to infer. Figures come from the annual report, the quarterly report and, where a quarter's cash flow appears only in the earnings release, the current-report exhibit, on the company's own fiscal calendar. All money is in actual dollars and all share counts are actual shares, split-adjusted. Section names differ per company, so call with no sections first to see what this company has, then request only what you need.
| Name | Type | Req | Description |
|---|---|---|---|
| sections | array | – | Top-level sections to return, for example annual, quarterly, trailing_twelve_months, notes, uncertainties. Omit for the whole file. An unknown name returns the valid list for that company. |
| ticker | string | yes | Ticker symbol, case-insensitive. Examples: NVDA, brk-b. |
No output schema declared.
No examples provided.
get_key_figures Headline figures for the latest period ~97
The headline figures for a company's most recent reported period: revenue, net income, diluted EPS and similar, each with its year-over-year change, the exact dollar amount, and the SEC accession number it came from. Start here for any 'how much did X earn' question. Far smaller than get_financials.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, case-insensitive. Examples: NVDA, brk-b. |
No output schema declared.
No examples provided.
get_narrative 10-K and 10-Q narrative ~161
Qualitative synthesis of a company's latest annual and quarterly reports, condensed from the filings themselves rather than from news: business description, risk factors with quarter-over-quarter changes flagged, MD&A, legal proceedings and subsequent events. Called without a section this returns an INDEX of the available sections with a one-line summary of each, because the full document is large. Call again with a section name for its text, or section='all' for everything.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Section name, matched case-insensitively on a prefix, for example 'risk'. Use 'all' for the complete document. Omit for the section index. |
| ticker | string | yes | Ticker symbol, case-insensitive. Examples: NVDA, brk-b. |
No output schema declared.
No examples provided.
list_companies List covered companies ~79
List the public companies Ticker Scout covers, with the fiscal period of the latest data and the predicted date of the next SEC filing. Call this first when you do not know whether a company is covered, or to turn a company name into a ticker.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional filter matched against ticker and company name, case-insensitive. |
No output schema declared.
No examples provided.
What is the ai.tickerscout/ticker-scout MCP server?
ai.tickerscout/ticker-scout is an MCP server listed in the public MCP registry as ai.tickerscout/ticker-scout. Agent-native SEC filing data: statements assembled, filings read and synthesized. No API key. This page covers its hosted endpoint (https://mcp.tickerscout.ai/mcp).
Is the ai.tickerscout/ticker-scout MCP server safe to use?
ai.tickerscout/ticker-scout scores 87 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 ai.tickerscout/ticker-scout MCP server expose?
ai.tickerscout/ticker-scout exposes 6 tools: list_companies, get_company, get_key_figures, get_financials, get_narrative, get_events. Their descriptions and schemas cost roughly 786 tokens of context every time the server is loaded.
Does the ai.tickerscout/ticker-scout MCP server require authentication?
No. We connected to ai.tickerscout/ticker-scout without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.tickerscout/ticker-scout MCP server still maintained?
ai.tickerscout/ticker-scout is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.