SudnoKontrol
REMOTE · API.SK.UKRFISH.ORG · SCANNED SEP 21
Ukrainian vessel registry: search by number/name/owner, full records, stats. No API key required.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 340 tokens (~85/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 (100% 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
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the SudnoKontrol MCP server?
SudnoKontrol is a hosted endpoint at https://api.sk.ukrfish.org/mcp, 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 · api.sk.ukrfish.org
claude mcp add --transport http org-ukrfish-sk-sudnokontrol 'https://api.sk.ukrfish.org/mcp'
{
"mcpServers": {
"org-ukrfish-sk-sudnokontrol": {
"url": "https://api.sk.ukrfish.org/mcp"
}
}
} {
"servers": {
"org-ukrfish-sk-sudnokontrol": {
"type": "http",
"url": "https://api.sk.ukrfish.org/mcp"
}
}
} [mcp_servers.org-ukrfish-sk-sudnokontrol] url = "https://api.sk.ukrfish.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-ukrfish-sk-sudnokontrol": {
"type": "remote",
"url": "https://api.sk.ukrfish.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-ukrfish-sk-sudnokontrol --url 'https://api.sk.ukrfish.org/mcp' --transport streamable-http
mcp_servers:
org-ukrfish-sk-sudnokontrol:
url: "https://api.sk.ukrfish.org/mcp" {
"McpServers": {
"org-ukrfish-sk-sudnokontrol": {
"Transport": "http",
"Url": "https://api.sk.ukrfish.org/mcp"
}
}
} assistant mcp add org-ukrfish-sk-sudnokontrol -t streamable-http -u 'https://api.sk.ukrfish.org/mcp'
{
"mcpServers": {
"org-ukrfish-sk-sudnokontrol": {
"type": "http",
"url": "https://api.sk.ukrfish.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 2026 · Probed https://api.sk.ukrfish.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sk.ukrfish.org | CN=YE2,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 66c1b73f7311b7599c68f3f534a9903c446 |
| SANs: api.sk.ukrfish.org, console.s3.sk.ukrfish.org, s3.sk.ukrfish.org, sk.ukrfish.org | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sk.ukrfish.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| ukrfish.org. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sk.ukrfish.org/mcp | Verified | 200 | |
| http (plaintext) | http://api.sk.ukrfish.org/mcp | HTTPS enforced | 301 | https://api.sk.ukrfish.org/mcp |
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 →
get_dataset_metadata Describe available vessel-registry datasets ~41
Describes available data sources (Державний судновий реєстр / Суднова книга), freshness (import dates), record counts, and available fields.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| api | object | yes | – |
| data_sources | array | yes | – |
| example_queries | array | yes | – |
| fields | array | yes | – |
No examples provided.
get_registry_stats Get aggregate vessel counts ~22
Aggregate public vessel counts for answering "how many vessels" questions.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| sources | array | yes | – |
| total_vessels | integer | yes | – |
No examples provided.
lookup_vessel Look up a Ukrainian vessel ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| registration_number | string | yes | Registration number, for example УПС-0129. |
| Name | Type | Req | Description |
|---|---|---|---|
| build_year | – | yes | – |
| home_port | – | yes | – |
| match | object | yes | – |
| name | string | yes | – |
| owner_address | – | yes | – |
| owner_name | – | yes | – |
| registration_number | string | yes | – |
| source | string | yes | – |
| source_name | string | yes | – |
| tonnage | – | yes | – |
| vessel_type | – | yes | – |
| web_url | string | yes | – |
No examples provided.
search_vessel_registries Search Ukrainian national vessel registries ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| build_year_max | integer | – | Inclusive maximum build year. |
| build_year_min | integer | – | Inclusive minimum build year. |
| home_port | string | – | Partial match on home port. |
| limit | integer | – | Page size. |
| offset | integer | – | Pagination offset. |
| q | string | – | Registration number, vessel name, or owner name. Accepts Latin or Cyrillic. |
| source | string | – | Dataset to search. |
| vessel_type | string | – | Partial match on vessel type (e.g. земснаряд). |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| total | integer | yes | – |
No examples provided.
What is the SudnoKontrol MCP server?
SudnoKontrol is an MCP server listed in the public MCP registry as org.ukrfish.sk/sudnokontrol. Ukrainian vessel registry: search by number/name/owner, full records, stats. No API key required. This page covers its hosted endpoint (https://api.sk.ukrfish.org/mcp).
Is the SudnoKontrol MCP server safe to use?
SudnoKontrol scores 87 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 SudnoKontrol MCP server expose?
SudnoKontrol exposes 4 tools: search_vessel_registries, lookup_vessel, get_registry_stats, get_dataset_metadata. Their descriptions and schemas cost roughly 340 tokens of context every time the server is loaded.
Does the SudnoKontrol MCP server require authentication?
No. We connected to SudnoKontrol without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SudnoKontrol MCP server still maintained?
SudnoKontrol is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.