COT-Reports
REMOTE · MCP.COT-REPORTS.COM
CFTC Commitments of Traders data for every CFTC futures market: positions, history, COT index.
Available components
Last scanned (15 hours ago)
Scores higher than 74% 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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1614 tokens (~179/item across 9 items; 9 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_markets” rewrote its description, which is the text the model reads security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
- Tool “get_cot_index” rewrote its description, which is the text the model reads security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 21 Nov 2026 · Probed https://mcp.cot-reports.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.cot-reports.com | CN=YR2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 6cb84d0c82bbe1ed1275e2ab442698be970 |
| SANs: *.cot-reports.com, cot-reports.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cot-reports.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| cot-reports.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://challenges.cloudflare.com https://js.stripe.com https://*.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://challenges.cloudflare.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-src https://challenges.cloudflare.com https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com; frame-ancestors 'self'; form-action 'self' https://checkout.stripe.com https://*.stripe.com; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cot-reports.com | Verified | 200 | |
| http (plaintext) | http://mcp.cot-reports.com | HTTPS enforced | 308 | https://mcp.cot-reports.com/ |
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 →
explain_cot Explain a COT concept ~65
A short explanation of a COT concept — the trader groups, net positions, open interest, the four report families, the COT index, release timing — with a link to the full guide. Available at every level.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | The concept to explain. |
No output schema declared.
No examples provided.
get_cot_index COT index for one market ~248
The COT index (0–100: where the current net position, as % of open interest, sits between its lowest and highest of the lookback window) for large speculators and commercials, from the Legacy report. Without an account: the 26- and 52-week windows; a free account, COT Premium and a Data API key: every window. Both CFTC variants (Futures Only and Futures & Options Combined) with COT Premium and Data API keys; without an account and with a free account, each report's default variant.
| Name | Type | Req | Description |
|---|---|---|---|
| lookback_weeks | – | – | Lookback window in weeks: 26, 52, 156 or 260. Default: 156 (3 years) — 52 without an account. |
| market | string | yes | A CFTC code (e.g. 099741), a ticker (e.g. 6E, GC) or a market name. |
| variant | string | – | CFTC variant: futonly = Futures Only, combined = Futures & Options Combined. Default: the report's own (Legacy: futonly; Disaggregated, TFF: combined; Supplemental is published combined only). |
No output schema declared.
No examples provided.
get_history COT history for one market ~325
Weekly COT history for one market, newest first: open interest and the net position of every trader group (up to 260 reports per call; page back with "until"). Without an account: Legacy, the last 26 reports (6 months). Free account: Legacy, the last 520 reports (10 years). COT Premium and Data API keys: every report family and the full history; COT Premium also adds close prices. A new COT Premium subscription that can still be withdrawn from reads the last year of what Premium adds, until the date in its confirmation e-mail. Both CFTC variants (Futures Only and Futures & Options Combined) with COT Premium and Data API keys; without an account and with a free account, each report's default variant.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Oldest report date to include, YYYY-MM-DD. |
| market | string | yes | A CFTC code (e.g. 099741), a ticker (e.g. 6E, GC) or a market name. |
| report | string | – | Report family: legacy (default), disaggregated, tff or supplemental. |
| reports | integer | – | How many weekly reports (default 12). |
| until | string | – | Newest report date to include, YYYY-MM-DD (for paging back). |
| variant | string | – | CFTC variant: futonly = Futures Only, combined = Futures & Options Combined. Default: the report's own (Legacy: futonly; Disaggregated, TFF: combined; Supplemental is published combined only). |
No output schema declared.
No examples provided.
get_latest_positions Latest COT positions for one market ~230
The latest COT report for one market: long, short and net positions of every trader group, the week-on-week change, % of open interest. Without an account and with a free account: the Legacy report. COT Premium and Data API keys: every report family (Legacy, Disaggregated, TFF, Supplemental); COT Premium also adds the close price. Both CFTC variants (Futures Only and Futures & Options Combined) with COT Premium and Data API keys; without an account and with a free account, each report's default variant.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | A CFTC code (e.g. 099741), a ticker (e.g. 6E, GC) or a market name. |
| report | string | – | Report family: legacy (default), disaggregated, tff or supplemental. |
| variant | string | – | CFTC variant: futonly = Futures Only, combined = Futures & Options Combined. Default: the report's own (Legacy: futonly; Disaggregated, TFF: combined; Supplemental is published combined only). |
No output schema declared.
No examples provided.
get_latest_snapshot Latest COT snapshot of every market ~188
The latest Legacy COT report of every market, 100 markets per answer (use offset for the next page): net positions of large speculators and commercials, their week-on-week change, and open interest. Filter by category. Available at every level. Both CFTC variants (Futures Only and Futures & Options Combined) with COT Premium and Data API keys; without an account and with a free account, each report's default variant.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category or subcategory, e.g. "Energy", "Stock Indices". |
| offset | integer | – | Paging: skip this many markets (default 0). |
| variant | string | – | CFTC variant: futonly = Futures Only, combined = Futures & Options Combined. Default: the report's own (Legacy: futonly; Disaggregated, TFF: combined; Supplemental is published combined only). |
No output schema declared.
No examples provided.
get_release_schedule COT release schedule ~57
Which COT report is the latest, when it was published, and when the next one is due (the CFTC publishes on Fridays at 3:30 pm Eastern for the Tuesday before; holidays move it). Available at every level.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_weekly_summary COT weekly summary ~144
The weekly summary of the 35 main markets (currencies, crypto, metals, energy, agriculture, stock indices) from the latest Legacy report: net positions of speculators and commercials and their change. Available at every level. Both CFTC variants (Futures Only and Futures & Options Combined) with COT Premium and Data API keys; without an account and with a free account, each report's default variant.
| Name | Type | Req | Description |
|---|---|---|---|
| variant | string | – | CFTC variant: futonly = Futures Only, combined = Futures & Options Combined. Default: the report's own (Legacy: futonly; Disaggregated, TFF: combined; Supplemental is published combined only). |
No output schema declared.
No examples provided.
list_markets List COT markets ~140
Lists the CFTC markets COT-Reports covers (370+): CFTC code, ticker, name, exchange, category and which report families exist for each. Filter by a search text, a category or a report family. Available at every level.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category or subcategory, e.g. "Metals", "Currencies & Forex". |
| limit | integer | – | At most 50 (default 25). |
| report | string | – | Report family: legacy (default), disaggregated, tff or supplemental. |
| search | string | – | Part of a name, ticker, alias or CFTC code. |
No output schema declared.
No examples provided.
scan_extremes Markets at positioning extremes ~113
Markets where large speculators are crowded long or short this week (the Crowding score: a blend of the 26-, 52- and 156-week percentiles of their net position as % of open interest; crowded long from 80 until it falls below 75, crowded short from 20 until it rises above 25), from the Legacy Futures Only report. COT Premium only, as on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| side | string | – | Crowded long, crowded short, or both (default). |
No output schema declared.
No examples provided.
How do I install the COT-Reports MCP server?
COT-Reports is a hosted endpoint at https://mcp.cot-reports.com/, 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.cot-reports.com
claude mcp add --transport http com-cot-reports-cot 'https://mcp.cot-reports.com/'
What is the COT-Reports MCP server?
COT-Reports is an MCP server listed in the public MCP registry as com.cot-reports/cot. CFTC Commitments of Traders data for every CFTC futures market: positions, history, COT index. This page covers its hosted endpoint (https://mcp.cot-reports.com).
Is the COT-Reports MCP server safe to use?
COT-Reports scores 79 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 COT-Reports MCP server expose?
COT-Reports exposes 9 tools: list_markets, get_latest_snapshot, get_latest_positions, get_history, get_cot_index, and 4 more. Their descriptions and schemas cost roughly 1,510 tokens of context every time the server is loaded.
Does the COT-Reports MCP server require authentication?
No. We connected to COT-Reports without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the COT-Reports MCP server still maintained?
COT-Reports 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 COT-Reports MCP server?
VerifyMCP ran 13 checks on COT-Reports, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.