_ registry / mcp streamable-http · checked 7h ago

romankryvolapov-mcp

https://mcp.romankryvolapov.com

Registry code: 1b1236120977cfdf

api record

Engineering blog of Roman Kryvolapov (romankryvolapov.com): Java, Kotlin, Android, Spring, microservices, Kubernetes, databases, LLMs; every article in English, Russian and Ukrainian. Use search (lang = the user’s language: en, ru or uk) to find articles, then fetch with a result id to read one in full. send_message emails the author: use it only when the user explicitly asks to contact him, with the user’s real name and email.

endpoint
https://mcp.romankryvolapov.com/
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is romankryvolapov-mcp live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is romankryvolapov-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does romankryvolapov-mcp have?
4 tools: fetch, get_page, send_message, search.
Is romankryvolapov-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
358ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search open 7h ago

    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, Russian and Ukrainian, 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ru",
            "uk"
          ],
          "type": "string",
          "description": "Language of the articles to return: en, ru or uk — normally the user’s language. Without it: English for a query in Latin script, Russian or Ukrainian for one in Cyrillic."
        },
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "How many articles to return."
        },
        "query": {
          "type": "string",
          "description": "Free-text search query, in any of the three languages."
        }
      }
    }
    arguments 28 lines
  • fetch unknown 7h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Article id from search: its canonical URL."
        }
      }
    }
    arguments 12 lines
  • get_page unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Canonical page URL."
        }
      }
    }
    arguments 12 lines
  • send_message unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "email",
        "message"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "ru",
            "uk"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the conversation: en, ru or uk. The reply comes in it."
        },
        "name": {
          "type": "string",
          "maxLength": 100,
          "description": "The sender’s name."
        },
        "email": {
          "type": "string",
          "format": "email",
          "maxLength": 254,
          "description": "The sender’s email address. The author replies to it."
        },
        "message": {
          "type": "string",
          "maxLength": 5000,
          "description": "The message, in any language."
        }
      }
    }
    arguments 36 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1b1236120977cfdf.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1b1236120977cfdf/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1b1236120977cfdf/badge.svg)](https://brick.blue/agent/1b1236120977cfdf?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.