# Bitrix MCP (remote · mcp-dev.bitrix24.com)

MCP server that delivers up-to-date Bitrix24 REST API documentation.

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp-dev.bitrix24.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/bitrix24-bitrix-mcp-rest/mcp-dev.md), [page](https://verifymcp.io/servers/bitrix24-bitrix-mcp-rest/mcp-dev)

## Channel facts

- Endpoint: `https://mcp-dev.bitrix24.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-08-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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 392 tokens (~78/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http bitrix24-bitrix-mcp-rest https://mcp-dev.bitrix24.com/mcp
```

### Codex

```toml
[mcp_servers.bitrix24-bitrix-mcp-rest]
url = "https://mcp-dev.bitrix24.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bitrix24-bitrix-mcp-rest": {
      "type": "remote",
      "url": "https://mcp-dev.bitrix24.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bitrix24-bitrix-mcp-rest --url https://mcp-dev.bitrix24.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bitrix24-bitrix-mcp-rest:
    url: "https://mcp-dev.bitrix24.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "bitrix24-bitrix-mcp-rest": {
      "type": "http",
      "url": "https://mcp-dev.bitrix24.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-08-04 (score 63, +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.

### 2026-08-02 (score 62, +1)

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

### 2026-07-31 (score 61, +2)

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

### 2026-07-30 (score 59, +1)

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

### 2026-07-28 (score 58, +1)

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

### 2026-07-27 (score 57, +1)

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

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (5)

### `bitrix-search` (~97 tokens)

Search Bitrix24 REST docs by natural-language query and return a short plain-text list of matches (method/event/article/app doc) with name, type, and brief description. Use the exact name/title from results when calling details tools. Optional filters: `limit` and `doc_type` (method|event|other|app_development_docs).

Input parameters:

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

Output parameters:

- `result` (string)

### `bitrix-app-development-doc-details` (~67 tokens)

Fetch Bitrix24 app development documentation by exact title (use `bitrix-search` with doc_type app_development_docs). Returns plain text labeled fields (Title, URL, Module, Category, Description, Content) without Markdown.

Input parameters:

- `title_or_hint` (string, required)

Output parameters:

- `result` (string)

### `bitrix-method-details` (~86 tokens)

Get details for a Bitrix24 REST method by exact name (use `bitrix-search` first). Returns plain text with labeled sections including parameters, returns, errors, and examples. Optional `field` limits output; `filter` narrows params by entity or examples by language.

Input parameters:

- `field` (string)
- `filter`
- `method` (string, required)

Output parameters:

- `result` (string)

### `bitrix-article-details` (~60 tokens)

Fetch a non-method Bitrix24 documentation article by exact title (use `bitrix-search` with doc_type other). Returns Markdown with title, metadata (URL/module/category), description, and content.

Input parameters:

- `title_or_hint` (string, required)

Output parameters:

- `result` (string)

### `bitrix-event-details` (~57 tokens)

Fetch Bitrix24 event documentation by exact event name (use `bitrix-search` with doc_type event). Returns Markdown with title, metadata (URL/module/category), description, and content.

Input parameters:

- `title_or_hint` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bitrix24-bitrix-mcp-rest/mcp-dev#diagnostics

## Score history

- 2026-08-04: 63
- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 61
- 2026-07-31: 61
- 2026-07-30: 59
- 2026-07-29: 58
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://mcp-dev.bitrix24.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/bitrix24-bitrix-mcp-rest/mcp-dev/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/bitrix24-bitrix-mcp-rest/mcp-dev/changelog.json
- HTML version of this page: https://verifymcp.io/servers/bitrix24-bitrix-mcp-rest/mcp-dev