# Chertov & Vorobyov physics problem solutions (remote · www.chertov.org.ua)

Read-only search and lookup over the Chertov & Vorobyov physics problem solutions (chertov.org.ua).

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `www.chertov.org.ua`: 77/100 (this document), [markdown](https://verifymcp.io/servers/ua-org-chertov-chertov/www.md), [page](https://verifymcp.io/servers/ua-org-chertov-chertov/www)

## Channel facts

- Endpoint: `https://www.chertov.org.ua/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-09-21.

- **Endpoint Security**: 63/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.
  - 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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1415 tokens (~235/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Chertov & Vorobyov physics problem solutions MCP server?

Chertov & Vorobyov physics problem solutions is a hosted endpoint at https://www.chertov.org.ua/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 ua-org-chertov-chertov 'https://www.chertov.org.ua/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ua-org-chertov-chertov": {
      "url": "https://www.chertov.org.ua/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ua-org-chertov-chertov": {
      "type": "http",
      "url": "https://www.chertov.org.ua/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ua-org-chertov-chertov]
url = "https://www.chertov.org.ua/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ua-org-chertov-chertov": {
      "type": "remote",
      "url": "https://www.chertov.org.ua/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ua-org-chertov-chertov --url 'https://www.chertov.org.ua/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ua-org-chertov-chertov:
    url: "https://www.chertov.org.ua/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ua-org-chertov-chertov": {
      "Transport": "http",
      "Url": "https://www.chertov.org.ua/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ua-org-chertov-chertov -t streamable-http -u 'https://www.chertov.org.ua/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ua-org-chertov-chertov": {
      "type": "http",
      "url": "https://www.chertov.org.ua/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-09-20 (score 77, +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-09-17 (score 76, +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-09-15 (score 75, +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.

### 2026-09-13 (score 74, +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.

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

### 2026-09-09 (score 72, +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-09-07 (score 71, +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-09-05 (score 70, +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.

## MCP tools (5)

### `list_chapters` (~99 tokens)

List Chapters

Map of the whole corpus: every chapter of the Chertov & Vorobyov physics problem book, with its paragraph (§) numbers and how many solved problems it holds. Takes no arguments. Returns JSON: {chapters: [{chapter, name, paragraph_count, paragraphs, paragraph_range, solved_problem_count, page_url}], totals: {chapters, paragraphs, solved_problems}}. Call this first to learn the shape of the corpus.

### `list_paragraphs` (~111 tokens)

List Paragraphs

Paragraphs (§) of the problem book, optionally restricted to one chapter. Arguments: chapter (optional integer). Returns JSON: {chapter, paragraphs: [{paragraph, name, chapter, chapter_name, solved_problem_count, problem_number_range, page_url}], totals: {paragraphs, solved_problems}}. Paragraph numbers are unique across the whole book, so a paragraph number alone addresses a section.

Input parameters:

- `chapter` (integer): Chapter number to restrict to. Omit for every paragraph in the book.

### `list_problems` (~200 tokens)

List Problems

Solved problems of one paragraph (§), paginated and in book order. Arguments: paragraph (required integer), page (optional, default 1), per_page (optional, default 25, max 100). Returns JSON: {paragraph, paragraph_name, chapter, chapter_name, problems: [{label, paragraph, number, chapter, condition, solution_image_url, page_url}], pagination: {page, per_page, total, total_pages}}. `condition` is the problem statement as plain Russian text; the worked solution exists only as the GIF at `solution_image_url`. Problems without a solution are not listed and are not counted.

Input parameters:

- `page` (integer): 1-based page number. Defaults to 1.
- `paragraph` (integer, required): Paragraph (§) number. Unique across the whole book; see list_paragraphs.
- `per_page` (integer): Results per page, 1 to 100. Defaults to 25.

### `get_problem` (~237 tokens)

Get Problem

One solved problem, in full. Address it either with paragraph + number, or with label — the spoken form "1.12" (a dot, a dash or a space also work: "1-12", "1 12"). Returns JSON: when found, {found: true, problem: {label, paragraph, number, chapter, condition, solution_image_url, page_url, chapter_name, paragraph_name, chapter_url, paragraph_url, solution_format}}; otherwise {found: false, reason: "not_solved"|"not_found", label, paragraph, number, message}. A missing or unsolved problem is a normal result, not an error — do not retry it.

Input parameters:

- `label` (string): The problem label as it is spoken or written: "1.12", "1-12" or "1 12". Use this OR paragraph + number.
- `number` (integer): Problem number within the paragraph. Give together with `paragraph`, or use `label` instead.
- `paragraph` (integer): Paragraph (§) number. Give together with `number`, or use `label` instead.

### `search_problems` (~217 tokens)

Search Problems

Full-text search over the Russian problem statements. Searches PROBLEMS ONLY — never articles or news. Arguments: query (required string, at least 5 characters once whitespace is removed), page (optional, default 1), per_page (optional, default 25, max 100). Returns JSON: {query, problems: [{label, paragraph, number, chapter, condition, solution_image_url, page_url}], pagination: {page, per_page, total, total_pages}}. Query in Russian — the statements are Russian. A shorter query is rejected with a validation error rather than returning nothing, and LIKE wildcards in the query are matched literally.

Input parameters:

- `page` (integer): 1-based page number. Defaults to 1.
- `per_page` (integer): Results per page, 1 to 100. Defaults to 25.
- `query` (string, required): Text to look for inside the problem statements, in Russian. At least 5 characters once all whitespace is removed — spaces do not count towards that minimum.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ua-org-chertov-chertov/www#diagnostics

## Score history

- 2026-09-21: 77
- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 69
- 2026-09-03: 69
- 2026-09-02: 69
- 2026-09-01: 68
- 2026-08-31: 68

## Common questions

### What is the Chertov & Vorobyov physics problem solutions MCP server?

Chertov & Vorobyov physics problem solutions is an MCP server listed in the public MCP registry as ua.org.chertov/chertov. Read-only search and lookup over the Chertov & Vorobyov physics problem solutions (chertov.org.ua). This page covers its hosted endpoint (https://www.chertov.org.ua/mcp).

### Is the Chertov & Vorobyov physics problem solutions MCP server safe to use?

Chertov & Vorobyov physics problem solutions scores 77 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 Chertov & Vorobyov physics problem solutions MCP server expose?

Chertov & Vorobyov physics problem solutions exposes 5 tools: list_chapters, list_paragraphs, list_problems, get_problem, search_problems. Their descriptions and schemas cost roughly 864 tokens of context every time the server is loaded.

### Does the Chertov & Vorobyov physics problem solutions MCP server require authentication?

No. We connected to Chertov & Vorobyov physics problem solutions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Chertov & Vorobyov physics problem solutions MCP server still maintained?

Chertov & Vorobyov physics problem solutions is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.chertov.org.ua/mcp
- Website: https://www.chertov.org.ua/mcp-api
- Changelog RSS feed: https://verifymcp.io/servers/ua-org-chertov-chertov/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/ua-org-chertov-chertov/www.json
- HTML version of this page: https://verifymcp.io/servers/ua-org-chertov-chertov/www