# BotOrNot (remote · getbotornot.com)

Is a trading bot legit? Sourced bot fact sheets, regulator scam records and on-chain results.

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

## Components

- remote · `getbotornot.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-getbotornot-botornot/getbotornot.md), [page](https://verifymcp.io/servers/com-getbotornot-botornot/getbotornot)

## Channel facts

- Endpoint: `https://getbotornot.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 938 tokens (~78/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 76/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 29% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the BotOrNot MCP server?

BotOrNot is a hosted endpoint at https://getbotornot.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.

### Claude

```bash
claude mcp add --transport http com-getbotornot-botornot 'https://getbotornot.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-getbotornot-botornot": {
      "url": "https://getbotornot.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getbotornot-botornot": {
      "type": "http",
      "url": "https://getbotornot.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-getbotornot-botornot]
url = "https://getbotornot.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getbotornot-botornot": {
      "type": "remote",
      "url": "https://getbotornot.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getbotornot-botornot --url 'https://getbotornot.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-getbotornot-botornot:
    url: "https://getbotornot.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-getbotornot-botornot": {
      "Transport": "http",
      "Url": "https://getbotornot.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getbotornot-botornot -t streamable-http -u 'https://getbotornot.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-getbotornot-botornot": {
      "type": "http",
      "url": "https://getbotornot.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 80, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-04 (score 79, +1)

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

### 2026-11-03 (score 78, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-02 (score 78, +1)

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

### 2026-10-30 (score 77, +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-28 (score 76, +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-26 (score 75, +1)

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

### 2026-10-24 (score 74, +1)

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

## MCP tools (12)

### `check_bot` (~99 tokens)

Check a trading bot name or website/domain against BotOrNot's sourced bot directory and every regulator scam record (SEC, CFTC and a state regulator crypto scam tracker). Returns a verdict (watchlist_match, documented_bot, both, no_record) with source URLs. no_record is NOT proof of safety.

Input parameters:

- `query` (string, required): Bot name or website, e.g. "3Commas" or "web3-cryptohopper.com"

### `get_bot` (~51 tokens)

Full sourced fact sheet for one documented bot by slug (see list_bots): pricing, markets, custody model, red flags with sources, report card, impostor scam reports.

Input parameters:

- `slug` (string, required)

### `get_report_card` (~66 tokens)

The rule-based BotOrNot report card for a bot (Clear record, Caution, Red flags, Closed, Limited data) with the exact sourced facts and rule ids that produced it. Not a rating or investment advice; payouts never change it.

Input parameters:

- `slug` (string, required)

### `get_prediction_markets` (~45 tokens)

Prediction-market venues (Kalshi, Polymarket US, Gemini Predictions) with their CFTC status and official sources, plus the documented prediction-market bots and their report cards.

### `list_bots` (~61 tokens)

List documented trading bots (slug, name, category, report card, official_url). Optionally filter by category or report card result.

Input parameters:

- `category` (string): Exact category name, e.g. "Prediction market bots"
- `result` (string)

### `compare_bots` (~42 tokens)

Side-by-side sourced facts and report cards for two bots by slug. No winner is picked.

Input parameters:

- `a` (string, required)
- `b` (string, required)

### `search_scams` (~65 tokens)

Search regulator scam and enforcement records (SEC, CFTC and a state regulator crypto scam tracker) by name, website or keyword. Every record has an official source URL. Regulator complaints are allegations until resolved.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `check_website` (~98 tokens)

Scam signals for a website: exact matches in a state regulator scam tracker, look-alikes of real bot domains (typos, homoglyphs, brand+words), domain age from public RDAP, HTTPS, and optional red-flag phrases in pasted text. Signals, not a verdict.

Input parameters:

- `text` (string): Optional text from the site or message to scan for regulator-listed red-flag phrases
- `url` (string, required)

### `get_changes` (~60 tokens)

Recent change events: new regulator cases, new state scam-tracker reports, bot shutdowns, report-card changes and keyword-matched SEC/CFTC releases. Optionally filter by bot slug.

Input parameters:

- `bot` (string)
- `limit` (integer)

### `check_telegram` (~106 tokens)

Check a Telegram @handle or t.me link: is it an official handle of a listed trading bot (verified on the bot's own site or docs), a known impersonator listed by the bot's own docs, a look-alike, or not in our records? Matches include custody model and incident history. A match is NOT a safety rating; unknown is not proof of a scam.

Input parameters:

- `handle` (string, required): @handle, t.me/ link or tg://resolve link

### `get_incidents` (~77 tokens)

Verified security incidents (hacks, exploits, key leaks) at trading bots: date, what happened, users affected, estimated loss as named in the sources, refund status and source URLs. Optionally filter by bot slug.

Input parameters:

- `bot` (string): Bot slug, e.g. "maestro"
- `limit` (integer)

### `get_leaderboard` (~61 tokens)

Hyperliquid vault leaderboard from on-chain data: open vaults with >= $100k TVL ranked by 30-day PnL (USD). Refreshed daily. Past results do not predict future ones.

Input parameters:

- `limit` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-getbotornot-botornot/getbotornot#diagnostics

## Score history

- 2026-11-06: 80
- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 72
- 2026-10-20: 72
- 2026-10-19: 71
- 2026-10-18: 71
- 2026-10-17: 70
- 2026-10-16: 69

## Common questions

### What is the BotOrNot MCP server?

BotOrNot is an MCP server listed in the public MCP registry as com.getbotornot/botornot. Is a trading bot legit? Sourced bot fact sheets, regulator scam records and on-chain results. This page covers its hosted endpoint (https://getbotornot.com/mcp).

### Is the BotOrNot MCP server safe to use?

BotOrNot 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 BotOrNot MCP server expose?

BotOrNot exposes 12 tools: check_bot, get_bot, get_report_card, get_prediction_markets, list_bots, and 7 more. Their descriptions and schemas cost roughly 831 tokens of context every time the server is loaded.

### Does the BotOrNot MCP server require authentication?

No. We connected to BotOrNot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BotOrNot MCP server still maintained?

BotOrNot 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 did VerifyMCP test on the BotOrNot MCP server?

VerifyMCP ran 13 checks on BotOrNot, 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.

## Links

- Remote endpoint: https://getbotornot.com/mcp
- Website: https://getbotornot.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-getbotornot-botornot/getbotornot.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getbotornot-botornot/getbotornot/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-getbotornot-botornot/getbotornot.json
- HTML version of this page: https://verifymcp.io/servers/com-getbotornot-botornot/getbotornot