# outcometick (npm · outcometick)

Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP

- Trust score: 88/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `outcometick.com`: 39/100, [markdown](https://verifymcp.io/servers/outcometick-outcometick/v1-mcp.md), [page](https://verifymcp.io/servers/outcometick-outcometick/v1-mcp)
- remote · `outcometick.com`: 80/100, [markdown](https://verifymcp.io/servers/outcometick-outcometick/v1-mcp-public.md), [page](https://verifymcp.io/servers/outcometick-outcometick/v1-mcp-public)
- npm · `outcometick`: 88/100 (this document), [markdown](https://verifymcp.io/servers/outcometick-outcometick/outcometick.md), [page](https://verifymcp.io/servers/outcometick-outcometick/outcometick)

## Channel facts

- Registry: `npm`
- Package: `outcometick`
- Version: `3.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 1 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to outcometick/outcometick-sdk-ts).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1127 tokens (~80/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add outcometick-outcometick -- npx -y outcometick mcp
```

### Cursor

```json
{
  "mcpServers": {
    "outcometick-outcometick": {
      "command": "npx",
      "args": [
        "-y",
        "outcometick",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "outcometick-outcometick": {
      "command": "npx",
      "args": [
        "-y",
        "outcometick",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add outcometick-outcometick -- npx -y outcometick mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "outcometick-outcometick": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "outcometick",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add outcometick-outcometick --command npx --arg -y --arg outcometick --arg mcp
```

### Hermes

```yaml
mcp_servers:
  outcometick-outcometick:
    command: "npx"
    args: ["-y", "outcometick", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "outcometick-outcometick": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "outcometick",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add outcometick-outcometick -t stdio -c npx -a -y outcometick mcp
```

### Other

```json
{
  "mcpServers": {
    "outcometick-outcometick": {
      "command": "npx",
      "args": [
        "-y",
        "outcometick",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 87, +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.

### 2026-11-02 (score 86, +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.

### 2026-10-31 (score 85, +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.

### 2026-10-29 (score 84, +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.

### 2026-10-27 (score 83, +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.

### 2026-10-25 (score 82, 0)

- [functional] Package version: 2.13.1 → 3.0.0

### 2026-10-24 (score 82, +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.

## MCP tools (14)

### `coverage` (~28 tokens)

What the archive holds, per venue: assets, datasets and the day range. Public, no key.

### `plans` (~20 tokens)

Data subscription plans and their live prices. Public, no key.

### `meta` (~47 tokens)

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.

### `list_files` (~286 tokens)

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.

Input parameters:

- `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".

### `download_file` (~102 tokens)

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.

Input parameters:

- `date` (string, required): YYYY-MM-DD (UTC)
- `dir` (string): Directory to save into (created if missing). Defaults to the current directory.
- `name` (string, required): File name exactly as list_files reports it

### `backtest_capacity` (~45 tokens)

Which days can be backtested on a venue right now (only the most recent window is sold), and how busy the queue is. Public.

Input parameters:

- `venue` (string, required)

### `backtest_quote` (~145 tokens)

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).

Input parameters:

- `assets` (array, required): 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, required)

### `check_strategy` (~54 tokens)

Validate a strategy directory (manifest.json plus source) with the exact validator the backtest queue runs. Local, free, no network, no key.

Input parameters:

- `dir` (string): The strategy directory. Defaults to the current directory.

### `backtest_runs` (~30 tokens)

Recent backtest runs under the configured backtest key (OT_BACKTEST_KEY), and the credit balance.

### `backtest_status` (~44 tokens)

One backtest run under the configured backtest key: status, scope, credits held and spent, and the report summary once done.

Input parameters:

- `run_id` (string, required)

### `smart_plans` (~37 tokens)

Smart-money plans (daily Polymarket wallet lists) and their live prices, and whether they are on sale. Public, no key.

### `smart_coverage` (~32 tokens)

How many smart-money days are published: the first and newest day, and the count. Public, no key.

### `smart_days` (~46 tokens)

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.

### `smart_download` (~93 tokens)

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.

Input parameters:

- `day` (string, required): YYYY-MM-DD (UTC)
- `dir` (string): Directory to save into (created if missing). Defaults to the current directory.
- `list` (string, required): top1000 needs the Top 1000 plan

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/outcometick-outcometick/outcometick#diagnostics

## Score history

- 2026-11-06: 88
- 2026-11-05: 87
- 2026-11-04: 87
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 84
- 2026-10-29: 84
- 2026-10-28: 83
- 2026-10-27: 83
- 2026-10-26: 82
- 2026-10-25: 82
- 2026-10-24: 82
- 2026-10-23: 81
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 66
- 2026-10-14: 49

## Common questions

### 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 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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 6 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.

## Links

- npm package: https://www.npmjs.com/package/outcometick
- Socket report: https://socket.dev/npm/package/outcometick
- Repository: https://github.com/outcometick/outcometick-sdk-ts
- Website: https://outcometick.com/docs/sdk
- Changelog RSS feed: https://verifymcp.io/servers/outcometick-outcometick/outcometick.xml
- Changelog JSON feed: https://verifymcp.io/servers/outcometick-outcometick/outcometick/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/outcometick-outcometick/outcometick.json
- HTML version of this page: https://verifymcp.io/servers/outcometick-outcometick/outcometick