SudnoKontrol
Registry code: 50fabb1e5acad805
Ukrainian vessel registry: search by number/name/owner, full records, stats. No API key required.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.sk.ukrfish.org/mcp
- 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 SudnoKontrol live?
- No — it has stopped answering the hub's checks (checked 2h ago). It answered 87% of checks over the last 30 days.
- Is SudnoKontrol free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does SudnoKontrol have?
- 4 tools: get_dataset_metadata, lookup_vessel, search_vessel_registries, get_registry_stats.
- Is SudnoKontrol 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.
90 days 92.6%· all time 92.6%
last good check
of 4 tools
- degraded → down· HTTP 502
- live → degraded· HTTP 502
- down → live
- degraded → down· fetch failed
- live → degraded· fetch failed
- used for
- look up a ukrainian vessel by registration number
- search vessel registries
- get vessel registry statistics
- takes → gives
- text → data
- tools
- 4 reads
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.
through this hub
successful
what callers paid
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_vessel_registries reads open 3d ago
Search public data from the Ukrainian State Ship Registry and Ship Book by free-text query and structured filters. Deterministic ordering with exact registration-number matches first. Handles Cyrillic and Latin scripts and separator-insensitive numbers (УПС-0129 ≡ УПС 0129 ≡ UPS-0129). Each result includes a web_url pointing to the public vessel information page.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "q": { "type": "string", "minLength": 2, "description": "Registration number, vessel name, or owner name. Accepts Latin or Cyrillic." }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Page size." }, "offset": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Pagination offset." }, "source": { "enum": [ "registry", "book", "both" ], "type": "string", "description": "Dataset to search." }, "home_port": { "type": "string", "description": "Partial match on home port." }, "vessel_type": { "type": "string", "description": "Partial match on vessel type (e.g. земснаряд)." }, "build_year_max": { "type": "integer", "maximum": 2100, "minimum": 1900, "description": "Inclusive maximum build year." }, "build_year_min": { "type": "integer", "maximum": 2100, "minimum": 1900, "description": "Inclusive minimum build year." } } }arguments 52 linesget_registry_stats reads open 3d ago
Aggregate public vessel counts for answering "how many vessels" questions.
{ "type": "object", "properties": {} }arguments 4 linesget_dataset_metadata reads unknown never probed
Describes available data sources (Державний судновий реєстр / Суднова книга), freshness (import dates), record counts, and available fields.
{ "type": "object", "properties": {} }arguments 4 lineslookup_vessel reads unknown 3d ago
Look up a vessel in the Ukrainian vessel registries using its registration number. Handles -, ., and space variance and Latin/Cyrillic forms. Returns the full public registry record, including a web_url pointing to the public vessel information page.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "registration_number" ], "properties": { "registration_number": { "type": "string", "minLength": 3, "description": "Registration number, for example УПС-0129." } } }arguments 14 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id50fabb1e5acad805.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/50fabb1e5acad805/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/50fabb1e5acad805?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.