Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Roman Kryvolapov Engineering Blog

REMOTE · MCP.ROMANKRYVOLAPOV.COM

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

+3 this week 69 Trust /100

Last scanned (21 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 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
  • Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 16 Nov 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.

  • 14 Nov 26 +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.

  • 13 Nov 26 0
    • 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 security
    • Server version: 1.3.0 → 1.4.0 functional
    • “search” reworded the description of “lang” cosmetic
    • “search” reworded the description of “query” cosmetic
    • “send_message” reworded the description of “lang” cosmetic
  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 64

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.romankryvolapov.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=romankryvolapov.com CN=WE1,O=Google Trust Services,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 d0f552c134ee816313baed275cd6e44c
SANs: romankryvolapov.com, mcp.romankryvolapov.com, *.mcp.romankryvolapov.com
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 mcp.romankryvolapov.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
romankryvolapov.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.romankryvolapov.com/ Verified 200
http (plaintext) http://mcp.romankryvolapov.com/ HTTPS enforced 301 https://mcp.romankryvolapov.com/
MCP tools · 4 exposed · ~497 tokens

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 →

Tool Tokens
fetch ~49

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

NameTypeReqDescription
idstringyesArticle id from search: its canonical URL.
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyesThe article as markdown.
titlestringyes–
urlstringyes–

No examples provided.

get_page ~67

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.

NameTypeReqDescription
urlstringyesCanonical page URL.

No output schema declared.

No examples provided.

search ~195

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.

NameTypeReqDescription
langstring–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.
limitinteger–How many articles to return.
querystringyesFree-text search query, in any of the site’s four languages.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

send_message ~186

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.

NameTypeReqDescription
emailstringyesThe sender’s email address. The author replies to it.
langstring–Language of the conversation: en, uk, ru or bg. The reply comes in it.
messagestringyesThe message, in any language.
namestringyesThe sender’s name.
NameTypeReqDescription
messagestringyes–
sentbooleanyes–

No examples provided.

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.

remote · mcp.romankryvolapov.com

# add to Claude Code
claude mcp add --transport http com-romankryvolapov-blog 'https://mcp.romankryvolapov.com/'
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.