Tickwind US Market Boards
REMOTE · API.TICKWIND.COM
No-API-key US market boards from SEC, Cboe, FINRA and CFTC: options flow, insiders, 13F, buybacks
Available components
Last scanned (16 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security63
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 690 tokens (~86/item across 8 items; 8 tools + 0 resources), lean.Pass
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 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
- 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
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 21 Nov 2026 · Probed https://api.tickwind.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tickwind.com | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 577352b28378a17b13920cb564c30625 |
| SANs: tickwind.com, *.tickwind.com | ||||||
| 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 insecure
Validation of api.tickwind.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tickwind.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://api.tickwind.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.tickwind.com/mcp | Inconclusive | 405 |
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 →
buyback_leaders ~102
US companies ranked by what they do to their own share count. view=cannibals ranks the largest latest-fiscal-year repurchase as a share of market cap; view=diluters ranks the fastest 1-year share-count growth. Source: company filings. The buyback figure is cash spent on repurchases as reported, NOT net of new issuance. Values: cannibals, diluters.
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | yes | which leaderboard to read |
No output schema declared.
No examples provided.
congress_trades ~67
Recently DISCLOSED stock trades by members of the US Congress, newest transaction first. Source: House and Senate periodic transaction reports, which may be filed up to 45 days after the trade — the newest disclosure is not the newest trade. Members disclose dollar amounts as ranges, never exact figures.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dca_rating ~79
A rules-based 0-100 read of how well one US stock fits scheduled recurring buying (dollar-cost averaging), computed from its disclosed filings and daily bars. Structural description only: it is not a recommendation, not a price target, and not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | US exchange ticker symbol, e.g. AAPL |
No output schema declared.
No examples provided.
insider_clusters ~83
US small caps where SEVERAL DISTINCT company insiders each bought their own stock on the open market in the last 30 days, ranked by number of buyers then dollar value. Source: SEC Form 4, open-market purchases only — grants and option exercises are excluded. Scanned over a $300M-$2.5B market-cap band, not the whole market.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
institutional_13f ~85
Which US stocks the tracked superinvestor funds added or opened last quarter, alongside how many trimmed or exited. Source: SEC form 13F, which reports LONG US equity positions as of a quarter end and is filed up to 45 days after it — these are historical positions, not current trades, and short positions, bonds and non-US holdings never appear in them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
key_levels ~84
Historical support and resistance price bands for one US stock, clustered from its daily bars (swing highs and lows plus volume shelves), with the nearest band above and below the latest close and how far away each sits. It describes where price HAS turned before and never forecasts whether a level will hold.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | US exchange ticker symbol, e.g. AAPL |
No output schema declared.
No examples provided.
risk_filings ~77
Recent SEC filings whose text MENTIONS a specific risk phrase, per EDGAR's full-text index. A mention is not a finding — the phrase also matches negations like "no material weakness". Values: going-concern, material-weakness, cyber-incident.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | which saved risk query to run |
No output schema declared.
No examples provided.
unusual_options ~53
Today's most-traded US single-stock option contracts by volume, with each contract's volume-to-open-interest ratio. Source: Cboe, ~15-minute delayed. Ranked within a fixed scan set, not the whole market.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Tickwind US Market Boards MCP server?
Tickwind US Market Boards is a hosted endpoint at https://api.tickwind.com/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 · api.tickwind.com
claude mcp add --transport http com-tickwind-tickwind 'https://api.tickwind.com/mcp'
What is the Tickwind US Market Boards MCP server?
Tickwind US Market Boards is an MCP server listed in the public MCP registry as com.tickwind/tickwind. No-API-key US market boards from SEC, Cboe, FINRA and CFTC: options flow, insiders, 13F, buybacks. This page covers its hosted endpoint (https://api.tickwind.com/mcp).
Is the Tickwind US Market Boards MCP server safe to use?
Tickwind US Market Boards scores 80 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 Tickwind US Market Boards MCP server expose?
Tickwind US Market Boards exposes 8 tools: buyback_leaders, congress_trades, dca_rating, insider_clusters, institutional_13f, and 3 more. Their descriptions and schemas cost roughly 630 tokens of context every time the server is loaded.
Does the Tickwind US Market Boards MCP server require authentication?
No. We connected to Tickwind US Market Boards without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tickwind US Market Boards MCP server still maintained?
Tickwind US Market Boards is still listed as active in the MCP registry. We last reached this channel on 21 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 Tickwind US Market Boards MCP server?
VerifyMCP ran 12 checks on Tickwind US Market Boards, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tickwind US Market Boards: HTTPS. 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.