Chertov & Vorobyov physics problem solutions
REMOTE · WWW.CHERTOV.ORG.UA · SCANNED SEP 20
Read-only search and lookup over the Chertov & Vorobyov physics problem solutions (chertov.org.ua).
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · www.chertov.org.ua
claude mcp add --transport http ua-org-chertov-chertov 'https://www.chertov.org.ua/mcp'
{
"mcpServers": {
"ua-org-chertov-chertov": {
"url": "https://www.chertov.org.ua/mcp"
}
}
} {
"servers": {
"ua-org-chertov-chertov": {
"type": "http",
"url": "https://www.chertov.org.ua/mcp"
}
}
} [mcp_servers.ua-org-chertov-chertov] url = "https://www.chertov.org.ua/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ua-org-chertov-chertov": {
"type": "remote",
"url": "https://www.chertov.org.ua/mcp",
"enabled": true
}
}
} openclaw mcp add ua-org-chertov-chertov --url 'https://www.chertov.org.ua/mcp' --transport streamable-http
mcp_servers:
ua-org-chertov-chertov:
url: "https://www.chertov.org.ua/mcp" {
"McpServers": {
"ua-org-chertov-chertov": {
"Transport": "http",
"Url": "https://www.chertov.org.ua/mcp"
}
}
} assistant mcp add ua-org-chertov-chertov -t streamable-http -u 'https://www.chertov.org.ua/mcp'
{
"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.
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.
- 20 Sept 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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 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.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
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 20 Sept 2026 · Probed https://www.chertov.org.ua/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chertov.org.ua | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b62292bfb61ebbac13d76c3362166b48 |
| SANs: chertov.org.ua, *.chertov.org.ua | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.chertov.org.ua. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ua. | present | 51024, 51024 | 13, 13 | Verified |
| org.ua. | present | 47066 | 13 | Verified |
| chertov.org.ua. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15768000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.chertov.org.ua/mcp | Verified | 200 | |
| http (plaintext) | http://www.chertov.org.ua/mcp | HTTPS enforced | 301 | https://www.chertov.org.ua/mcp |
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 →
get_problem Get Problem ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_chapters List Chapters ~99
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_paragraphs List Paragraphs ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chapter | integer | – | Chapter number to restrict to. Omit for every paragraph in the book. |
No output schema declared.
No examples provided.
list_problems List Problems ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number. Defaults to 1. |
| paragraph | integer | yes | Paragraph (§) number. Unique across the whole book; see list_paragraphs. |
| per_page | integer | – | Results per page, 1 to 100. Defaults to 25. |
No output schema declared.
No examples provided.
search_problems Search Problems ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number. Defaults to 1. |
| per_page | integer | – | Results per page, 1 to 100. Defaults to 25. |
| query | string | yes | 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. |
No output schema declared.
No examples provided.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.