SudnoKontrol MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host interface for the HTTP transport, e.g. 127.0.0.1. | |
| PORT | No | Port for the HTTP transport. Defaults to 8958 when running in HTTP mode. | 8958 |
| SUDNOKONTROL_API | No | Base URL of the SudnoKontrol API that the MCP server proxies. Overrides the default public API endpoint, e.g. https://api.sk.ukrfish.org/api/ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_vessel_registriesA | Search Державний судновий реєстр України and Суднова книга України by free-text query and structured filters. Deterministic ordering with exact registration-number matches first. Each result includes a web_url linking to the public site for ordering an official registry excerpt. |
| lookup_vesselA | Exact vessel lookup by normalized registration number (handles -, ., and space variance, and Latin/Cyrillic forms). Returns full registry data plus a web_url to the public site for ordering an official excerpt. |
| get_registry_statsA | Aggregate public vessel counts for answering "how many vessels" questions. |
| get_dataset_metadataA | Describes available data sources (Державний судновий реєстр / Суднова книга), freshness (import dates), record counts, and available fields. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: dataset metadata, free-text search, exact registration-number lookup, and aggregate statistics. No overlaps in function; even search and lookup are clearly separated by exact vs. fuzzy matching.
All tool names follow the same verb_noun snake_case convention: get_dataset_metadata, search_vessel_registries, lookup_vessel, get_registry_stats. Consistent and predictable.
4 tools is well-scoped for a read-only registry API. Each tool covers a necessary operation without redundancy or bloat.
The surface fully covers the domain's read-side: metadata discovery, flexible search, exact lookup, and statistics. No essential operations are missing for the stated purpose.