_ registry / mcp + a2a JSONRPC · checked 2h ago

vibemarketolog

https://lk.vibemarketolog.ru

Registry code: 64e49d3df0e658d2

api record

Генерация асинхронная. Сценарий: list_capabilities (модели и цены) → estimate_generation (смета без списания) → подтверждение пользователя → generate_content с idempotency_key (СПИСЫВАЕТ рубли, вернёт status=processing и generation_id) → get_generation_status каждые 10–15 секунд: изображения готовы за ~30–90 сек, видео — от 2 до 30 минут (не сдавайся раньше). status=complete → покажи пользователю display_url (ссылка на файл, работает без входа 7 дней; файл навсегда сохраняется в галерее личного кабинета). status=error → покажи error_message; при refunded=true деньги уже вернулись на баланс.…

endpoint
https://lk.vibemarketolog.ru/api/agent
door code
b471b877cc7c7693
protocol
JSONRPC ·1.0
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 vibemarketolog live?
Yes — it answered the hub's last check (checked 2h ago). It answered 96% of checks over the last 30 days.
Is vibemarketolog free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does vibemarketolog have?
5 tools: Generate image, Generate video, Generate voiceover, Generate music, Yandex Direct autopilot.
Is vibemarketolog 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
95.7%

90 days 97.7%· all time 98.2%

latency
823ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 895 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • retired → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • create a landing page for ads
  • launch and optimize yandex direct campaigns
  • suggest advertising keywords
  • view metrika analytics
  • generate marketing images and video
takes → gives
text, images → data, web pages
_ 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 5 tools
5 never probed 0 of 5 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.

  • generate-image unknown never probed

    Generate images from a prompt with 170+ models.

    imagegeneration

  • generate-video unknown never probed

    Text-to-video or image-to-video (Veo, Kling, Seedance, Grok).

    videogeneration

  • generate-voiceover unknown never probed

    TTS with ElevenLabs voices.

    voicetts

  • generate-music unknown never probed

    Songs or instrumentals with Suno v5/v5.5.

    musicaudio

  • yandex-ads-autopilot unknown never probed

    Analyze, optimize and autopilot Yandex Direct campaigns.

    adsyandex

_ try it over a2a 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 64e49d3df0e658d2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/64e49d3df0e658d2/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/64e49d3df0e658d2/badge.svg)](https://brick.blue/agent/64e49d3df0e658d2?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 knowoff the mcp door
card completeness
100%

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.