# Roman Kryvolapov Engineering Blog (remote · mcp.romankryvolapov.com)

Search and read romankryvolapov.com engineering articles; message the author.

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

## Components

- remote · `mcp.romankryvolapov.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-romankryvolapov-blog/mcp.md), [page](https://verifymcp.io/servers/com-romankryvolapov-blog/mcp)

## Channel facts

- Endpoint: `https://mcp.romankryvolapov.com/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.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-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_message).
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 608 tokens (~152/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
  - Structured output schemas are declared (75% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Roman Kryvolapov Engineering Blog MCP server?

Roman Kryvolapov Engineering Blog is a hosted endpoint at https://mcp.romankryvolapov.com/, 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-romankryvolapov-blog 'https://mcp.romankryvolapov.com/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-romankryvolapov-blog": {
      "url": "https://mcp.romankryvolapov.com/"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-romankryvolapov-blog]
url = "https://mcp.romankryvolapov.com/"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-romankryvolapov-blog:
    url: "https://mcp.romankryvolapov.com/"
```

### Netclaw

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

### Vellum

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

### Other

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

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-21 (score 69, +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-11-19 (score 68, +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.

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

### 2026-11-14 (score 66, +1)

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

### 2026-11-13 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [functional] Server version: 1.3.0 → 1.4.0
- [cosmetic] “search” reworded the description of “lang”
- [cosmetic] “search” reworded the description of “query”
- [cosmetic] “send_message” reworded the description of “lang”

### 2026-11-12 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 64)

First indexed and scored.

## MCP tools (4)

### `search` (~195 tokens)

Search the blog

Search the romankryvolapov.com engineering blog: articles on Java, Kotlin, Android, Spring, microservices, gRPC, Kubernetes, databases, and running large language models locally (llama.cpp, LoRA fine-tuning, RAG, prompt engineering). Every article exists in English, Ukrainian, Russian and Bulgarian, and results come in one language: set lang to the user’s language, otherwise it is guessed from the query. Returns matching articles with snippets and URLs; read one with fetch, passing its id.

Input parameters:

- `lang` (string): Language of the articles to return: en, uk, ru or bg — normally the user’s language. Without it: English for a query in Latin script, Ukrainian, Russian or Bulgarian for one in Cyrillic.
- `limit` (integer): How many articles to return.
- `query` (string, required): Free-text search query, in any of the site’s four languages.

Output parameters:

- `results` (array)

### `fetch` (~49 tokens)

Read an article

Return the full text of one article by the id from search results (its canonical URL), as markdown with code listings preserved verbatim.

Input parameters:

- `id` (string, required): Article id from search: its canonical URL.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string): The article as markdown.
- `title` (string)
- `url` (string)

### `get_page` (~67 tokens)

Read an article (plain text)

Return the full markdown of one article by its canonical URL (e.g. https://romankryvolapov.com/ru/ktor-manual/). Code listings are preserved verbatim. The same as fetch, as plain text.

Input parameters:

- `url` (string, required): Canonical page URL.

### `send_message` (~186 tokens)

Send a message to the author

Send a message to Roman Kryvolapov, the author of this blog: a question about one of the articles, a suggestion for a new article, or a job or project offer. It goes to his inbox, and he replies by email to the address given. Use it only when the user asked to contact the author, with the user’s own name and email address — never invent them — and show the user the text before sending. At most 20 messages a day are accepted from all agents together, and 3 from one email address.

Input parameters:

- `email` (string, required): The sender’s email address. The author replies to it.
- `lang` (string): Language of the conversation: en, uk, ru or bg. The reply comes in it.
- `message` (string, required): The message, in any language.
- `name` (string, required): The sender’s name.

Output parameters:

- `message` (string)
- `sent` (boolean)

## Diagnostics

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

## Score history

- 2026-11-21: 69
- 2026-11-20: 68
- 2026-11-19: 68
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 67
- 2026-11-15: 66
- 2026-11-14: 66
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 64

## Common questions

### What is the Roman Kryvolapov Engineering Blog MCP server?

Roman Kryvolapov Engineering Blog is an MCP server listed in the public MCP registry as com.romankryvolapov/blog. Search and read romankryvolapov.com engineering articles; message the author. This page covers its hosted endpoint (https://mcp.romankryvolapov.com/).

### Is the Roman Kryvolapov Engineering Blog MCP server safe to use?

Roman Kryvolapov Engineering Blog scores 69 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 Roman Kryvolapov Engineering Blog MCP server expose?

Roman Kryvolapov Engineering Blog exposes 4 tools: search, fetch, get_page, send_message. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.

### Does the Roman Kryvolapov Engineering Blog MCP server require authentication?

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

### Is the Roman Kryvolapov Engineering Blog MCP server still maintained?

Roman Kryvolapov Engineering Blog is still listed as active in the MCP registry. We last reached this channel on 21 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 Roman Kryvolapov Engineering Blog MCP server?

VerifyMCP ran 13 checks on Roman Kryvolapov Engineering Blog, 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://mcp.romankryvolapov.com/
- Website: https://romankryvolapov.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-romankryvolapov-blog/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-romankryvolapov-blog/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-romankryvolapov-blog/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-romankryvolapov-blog/mcp
