
OceanSphere MCP server
Which MCP servers are OceanSphere's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-03
- Registry nameio.oceansphere.engines/equipment-libraryverified in the MCP registry
The registry name sits under oceansphere.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-03
- Tools5
- Server calls itselfoceansphere-engines
- Server version1.0.0
- Protocol version2025-06-18
On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 535 ms.
- Its tools do none of the product's use cases we checked: request a spare part when own suppliers cannot supply it; find vetted specialists for engine overhauls and deck machinery.
- Checked on 2 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- What an agent can do with it0 of 2 use cases
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer548 ms
- Space in an agent's context≈ 1,205 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- cannot · request a spare part when own suppliers cannot supply it
- not sure · look up which equipment model sits where on a ship
- cannot · find vetted specialists for engine overhauls and deck machinery
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_equipment_modelsSearch the OceanSphere equipment library (marine engines, auxiliaries, pumps, deck machinery, navigation and electrical equipment) by model designation, equipment type or keywords; optionally filter by manufacturer, ship_area or category…
get_equipment_modelGet one library model (model_ref from a search, or manufacturer + exact designation): category, ship area, page URL, manufacturer datasheet link if any, and the stored technical characteristics. Each value has source_document (label of…
find_by_manufacturerList models of one manufacturer, best-documented first, at most 8 per call and no paging (total_matches shows the size). Narrow with category or ship_area, or use search_equipment_models with a designation to reach a specific model.
list_ship_areasList the ship areas of the library (engine room, deck, electrical, navigation, safety, cargo, HVAC) with model counts.
list_categoriesList the equipment categories with model counts, optionally for one ship_area. Use the names as category filter.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"equipment-library": {
"type": "http",
"url": "https://engines.oceansphere.io/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http oceansphere https://engines.oceansphere.io/mcpclaude.ai, ChatGPT and other clients: add https://engines.oceansphere.io/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.