Chertov & Vorobyov physics problem solutions

ua.org.chertovPublished by chertov.org.uaOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Read-only lookup of the Chertov & Vorobyov physics problem book: browse chapters and paragraphs, list solved problems, fetch one solution, and full-text…

What you can do
  • Browse the book structure: list every chapter with paragraph numbers and solved-problem counts
  • List paragraphs, optionally limited to one chapter, with problem-number ranges
  • List solved problems of a paragraph in book order, paginated
  • Fetch one problem in full by paragraph and number, or by label such as 1.12
  • Full-text search over the Russian problem statements, paginated
When to use it
Useful when someone works with this specific Russian physics problem book and wants an assistant to locate problems by chapter, paragraph, number or keyword and pull up the statement and solution image link.
Requirements
Remote streamable HTTP endpoint at the provider's site; no authentication, environment variables or headers declared. Network access to the provider is needed.
Before you install
Read-only: the tools only list, fetch and search, with no writing or deletion. Problem statements are in Russian, and search needs a query of at least five characters. Results link to pages and solution images hosted by the third-party site.

Installation

In SourceWeft

  1. Open Chertov & Vorobyov physics problem solutions in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ua.org.chertov%2Fchertov/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "chertov-vorobyov-physics-problem-solutio": {
      "type": "http",
      "url": "https://www.chertov.org.ua/mcp"
    }
  }
}

Tools

5

list_chapters

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.

Takes no parameters.

list_paragraphs

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.

Parameterschapter

list_problems

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.

Parameterspageper_pageparagraphrequired

get_problem

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.

Parameterslabelnumberparagraph

search_problems

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.

Parameterspagequeryrequiredper_page

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.