outcometick
NPM · OUTCOMETICK · 3 COMPONENTS
Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Available components
Last scanned (6 hours ago)
Scores higher than 91% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to outcometick/outcometick-sdk-ts). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1127 tokens (~80/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 4 Nov 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Package version: 2.13.1 → 3.0.0 functional
- 24 Oct 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.
- 23 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
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 5 Nov 2026 · Analysed npm/outcometick@3.0.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | outcometick/outcometick-sdk-ts |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/outcometick/outcometick-sdk-ts/.github/workflows/publish.yml@refs/tags/v3.0.0 |
| Rekor log index | 3264878576 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:94a8b50976d3ab7b91bf89d29085c8c26d761792d867dcc84ecb6e8c9921649a1d7fc6106b08cdd8ba0941b521156be2d48d0c29cdbb698a1e0e7fdd2 |
Background: How many MCP packages publish verified provenance →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
backtest_capacity ~45
Which days can be backtested on a venue right now (only the most recent window is sold), and how busy the queue is. Public.
| Name | Type | Req | Description |
|---|---|---|---|
| venue | string | yes | – |
No output schema declared.
No examples provided.
backtest_quote ~145
Price a backtest scope in credits (1 credit = 1 market-day) without submitting anything. Public. Give either from/to or days (the most recent n archived days).
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | yes | Base symbols, e.g. ["BTC","ETH"] |
| days | integer | – | – |
| from | string | – | YYYY-MM-DD (UTC) |
| intervals | array | – | – |
| language | string | – | Runtime from the manifest, e.g. "python@3.14" or "nodejs@24"; changes how many market-days one run may hold |
| to | string | – | YYYY-MM-DD (UTC) |
| venue | string | yes | – |
No output schema declared.
No examples provided.
backtest_runs ~30
Recent backtest runs under the configured backtest key (OT_BACKTEST_KEY), and the credit balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
backtest_status ~44
One backtest run under the configured backtest key: status, scope, credits held and spent, and the report summary once done.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
check_strategy ~54
Validate a strategy directory (manifest.json plus source) with the exact validator the backtest queue runs. Local, free, no network, no key.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | The strategy directory. Defaults to the current directory. |
No output schema declared.
No examples provided.
coverage ~28
What the archive holds, per venue: assets, datasets and the day range. Public, no key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
download_file ~102
Download one archive file into a local directory and verify its sha256. Never overwrites: if the file is already there, delete it first. Files are gzipped CSV or JSONL; take date and name from list_files.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | YYYY-MM-DD (UTC) |
| dir | string | – | Directory to save into (created if missing). Defaults to the current directory. |
| name | string | yes | File name exactly as list_files reports it |
No output schema declared.
No examples provided.
list_files ~286
Search archive files the data key can download. Every filter is optional; without a date it lists the newest day in reach. asset is the BASE symbol (BTC, not BTCUSD). interval "5m" EXCLUDES the period-less settlement streams (prices, twap30s, twap60s); pass ["5m","none"] to get both. Ranges are capped at 92 days.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | – | – | Base symbol, e.g. BTC. A list means "any of these". |
| dataset | – | – | e.g. prices, twap60s, book, markets, last_trade_price, klines, orderbook. A list means "any of these". |
| date | string | – | YYYY-MM-DD (UTC) |
| format | string | – | parquet lists the Parquet copy of each file (same rows, already typed); default gz, the archive files |
| from | string | – | YYYY-MM-DD (UTC) |
| interval | – | – | e.g. 5m, 15m, 1m, or "none" for period-less files. A list means "any of these". |
| limit | integer | – | Rows to return (default 200); count and bytes always cover everything matched. |
| to | string | – | YYYY-MM-DD (UTC) |
| venue | – | – | polymarket | predict. A list means "any of these". |
No output schema declared.
No examples provided.
meta ~47
The date window the configured data key (OT_KEY) can download, and every venue, asset, interval and dataset value inside it. Call this before list_files: it names the real filter values.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plans ~20
Data subscription plans and their live prices. Public, no key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smart_coverage ~32
How many smart-money days are published: the first and newest day, and the count. Public, no key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smart_days ~46
The days the configured smart-money key (OT_SMART_KEY) can download, newest first, with each list's status, rows, bytes and sha256. Call this before smart_download.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smart_download ~93
Download one day's smart-money list (zstd-compressed CSV) into a local directory and verify its sha256. Never overwrites. Take day and list from smart_days.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | yes | YYYY-MM-DD (UTC) |
| dir | string | – | Directory to save into (created if missing). Defaults to the current directory. |
| list | string | yes | top1000 needs the Top 1000 plan |
No output schema declared.
No examples provided.
smart_plans ~37
Smart-money plans (daily Polymarket wallet lists) and their live prices, and whether they are on sale. Public, no key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the outcometick MCP server?
outcometick runs locally as an npm package, launched with npx -y outcometick mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · outcometick
claude mcp add outcometick-outcometick -- npx -y outcometick mcp
What is the outcometick MCP server?
outcometick is an MCP server listed in the public MCP registry as io.github.outcometick/outcometick. Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP. This page covers its npm package (outcometick).
Is the outcometick MCP server safe to use?
outcometick scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 outcometick MCP server expose?
outcometick exposes 14 tools: coverage, plans, meta, list_files, download_file, and 9 more. Their descriptions and schemas cost roughly 1,009 tokens of context every time the server is loaded.
Is the outcometick MCP server still maintained?
outcometick 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 licence is the outcometick MCP server under?
outcometick declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the outcometick MCP server?
VerifyMCP ran 16 checks on outcometick, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.