Seamark
REMOTE · SEAMARK.APP
Personal sailing voyage log: trips, legs, ships, crew and GPX tracks with honest statistics.
Available components
Last scanned (22 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3754 tokens (~250/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 0
- Server version: 2.9.0 → 2.9.1 functional
- 18 Nov 26 0
- Stability: 0.97 → pass security
- 17 Nov 26 0
- Stability: pass → 0.97 functional
- 16 Nov 26 −1
- New tool “diary_write”, which the server declares destructive security
- Tool “leg_write” rewrote its description, which is the text the model reads security
- Tool “track_write” rewrote its description, which is the text the model reads security
- Tool “trip_read” rewrote its description, which is the text the model reads security
- Tool “trip_write” rewrote its description, which is the text the model reads security
- Schema quality: 3059 → 3754 ▼ functional
- Server version: 2.8.0 → 2.9.0 functional
- New tool “diary_read” functional
- 12 Nov 26 0
- Tool “leg_write” rewrote its description, which is the text the model reads security
- Server version: 2.6.1 → 2.8.0 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 7 Nov 26 +1
- Stability: 0.97 → pass security
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 Nov 2026 · Probed https://seamark.app/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=seamark.app | CN=YE1,O=Let's Encrypt,C=US | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 60e6741eab30999fa7e00b72e300d17ab7a |
| SANs: seamark.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 seamark.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| seamark.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://seamark.app/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://seamark.app/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'none';img-src 'self' data: https://tile.openstreetmap.org https://tiles.openseamap.org;object-src 'none';script-src 'self' https://um.tallship.cz;script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests;connect-src 'self' https://um.tallship.cz |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://seamark.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://seamark.app/mcp |
| Authorisation server | https://seamark.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://seamark.app/mcp | Verified | 200 | |
| http (plaintext) | http://seamark.app/mcp | HTTPS enforced | 301 | https://seamark.app/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 →
diary_read Read the diary ~187
Read a trip's diary: list its entries (by date, oldest first), or get one day's entry. Works on the caller's own trips and on trips shared with them as linked crew. A day without an entry is not_found. A trip's diary holds at most one entry per calendar day of the trip, addressed by the trip id and the date (YYYY-MM-DD, the trip's local calendar date, between the trip's startDate and endDate inclusive). An entry's `body` is plain text (1-8000 characters, not only whitespace; line breaks are kept). `public` says whether the entry shows on the trip's public share page; the owner and linked crew see every entry either way. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
diary_write Change the diary ~335
Write or remove one day's entry in a trip's diary; owner only. `put` creates the day's entry or replaces it whole: `entry.public` defaults to false when omitted, so leave it out only to take an entry off the public share page. A date outside the trip's dates is validation_failed. `delete` removes the day's entry; deleting a day that has none succeeds and changes nothing. Both take an optional `expectedUpdatedAt` (the entry's updatedAt as you read it): if the entry changed or was removed since, nothing is written and the answer is stale_write with the current version (`actual`, or null when the day has no entry). To write a day you saw empty without overwriting an entry someone else wrote meanwhile, `put` with `expectedAbsent: true` instead (never together with `expectedUpdatedAt`, which is bad_request); a day that has an entry by then answers stale_write with its version as `actual`. A trip's diary holds at most one entry per calendar day of the trip, addressed by the trip id and the date (YYYY-MM-DD, the trip's local calendar date, between the trip's startDate and endDate inclusive). An entry's `body` is plain text (1-8000 characters, not only whitespace; line breaks are kept). `public` says whether the entry shows on the trip's public share page; the owner and linked crew see every entry either way. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
leg_read Read legs ~191
Read a trip's ordered legs: list them, or get one by id. A leg's `statsSource` is 'track' when its stats, coordinates and times are computed from a GPX track, 'manual' otherwise. On a trip someone else shared with the caller, `get` reads a leg but `list` does not — its legs are in `trip_read`'s `get`. The weather fields are hand-entered observations, except the wind pair when `weatherSource` is 'open_meteo': windSpeedKn is true wind speed in knots, windDirDeg an integer 0-359 in meteorological convention (the direction the wind blows FROM), seaState the Douglas degree of sea 0-9. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
leg_write Change legs ~571
Change a trip's ordered legs: create, update, delete, reorder (a full leg-id permutation, reassigning seq 1..N), and fill a leg's wind from a weather service (fetch_weather). A leg backed by a track (statsSource: 'track') rejects an update that touches any computed stats/coordinate/time field with a stats_readonly error — its startName/endName/notes stay editable regardless. A leg spans at most 60 days from startTime to endTime (24-hour days, exactly 60 allowed); longer is leg_too_long (422) on create and on an update that changes a time — split a longer passage into several legs. The weather fields are hand-entered observations, except the wind pair when `weatherSource` is 'open_meteo': windSpeedKn is true wind speed in knots, windDirDeg an integer 0-359 in meteorological convention (the direction the wind blows FROM), seaState the Douglas degree of sea 0-9. They stay editable on EVERY leg, track-backed or not, because no GPX file records them. `fetch_weather` fills the leg's WIND (speed and direction, never sea state) from the free Open-Meteo service: it resolves the position and time window from the leg's own data (its track's middle point, else its endpoint midpoint, else its start) and stores the arithmetic mean of the hourly speeds over that window plus their SPEED-WEIGHTED circular mean direction, stamping weatherSource 'open_meteo' and weatherFetchedAt — except when the window was a dead calm, which yields no direction: a hand-entered windDirDeg then survives and the response says weatherSource 'manual' instead, because the stamp must never attribute a hand-typed value to the provider. This is the ONLY action that makes an outbound network call on the caller's behalf, it is rate-limited to 30 per hour per user, and it overwrites whatever wind the leg already had, hand-entered included — unless the leg changes while the provider is being asked, in which case nothing is written and it answers stale_write with the current version (the concurrent edit wins; cal…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
person_read Read people ~132
Read the caller's private address book of people — crew and contacts: list them all, or get one by id. Personal data (birth date, passport) is never shared across users. `linkedAccount` reports whether this person has accepted an invitation and is linked to a Seamark account. `isSelf` marks the ONE person in the caller's book that is the caller, so voyages with them on the crew list count as the caller's own. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
person_write Change people ~505
Change the caller's private address book of people — crew and contacts (create, update, delete, unlink_account, mark_self, unmark_self, invite, accept_invitation). Personal data (birth date, passport) is never shared across users. `linkedAccount` reports whether this person has accepted an invitation and is linked to a Seamark account. `isSelf` marks the ONE person in the caller's book that is the caller, so voyages with them on the crew list count as the caller's own. `invite` mails a Seamark invitation to a person who crews at least one of the caller's trips (409 `invitation_no_trips` otherwise — the person must be on a trip's crew first); accepting it links their account to this person, which opens EVERY trip of the caller's they crew, past and future, so the mail lists all of them. It is rate-limited to one send per person per minute and 3 sends per recipient address per hour (a budget shared with trip_write's `announce`, keyed on the address rather than the feature), remembers the address on the person's `email` (advancing the person's `updatedAt` version token — the response carries the new value), and re-inviting replaces the previous invitation, so a mistyped address's link stops working. `accept_invitation` is the other side: it binds the CALLER's own account to the person named by the token, requires the caller's address to match the one invited, and returns every trip it opened. `unlink_account` revokes a person's account link everywhere at once AND cancels any invitation to that person that has not been accepted yet — a pending invite mail stops working, which is what makes the revocation final rather than something the other party can undo by re-clicking their link. It is idempotent, and on someone who was never linked its only effect is to cancel a pending invitation. `mark_self` sets `isSelf` (marking someone new moves the marker off whoever held it — at most one person is the caller), `unmark_self` clears it. Both are idempotent and unrelated to `li…
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resume Sailing résumé ~271
The caller's sailing résumé — the record a charter company asks for before handing over a boat: one row per voyage the caller sailed with a known role, newest first, each with start and end date, the boat (name, model, length overall in centimeters as `loaCm`, hull type, or null when the voyage has no boat), the caller's role ('skipper' or 'crew'), ports-of-call countries (ISO 3166-1 alpha-2) and sea areas in voyage order, distance in meters, days at sea and night time in seconds. Totals cover the returned rows, overall and per role. Optional `role` ('all', 'skipper', 'crew') filters the rows; optional `from`/`to` (YYYY-MM-DD, inclusive) bound them by start date. Voyages where the caller is not on the crew have no role, are left out, and are counted as `unattributedTripsCount`. The figures come from the caller's own log and are not verified by anyone else. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| role | – | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
ship_read Read boats ~130
Read the caller's boats — a reusable, per-owner registry: list them all, or get one by id. The optional `flag` field is a ship's flag state as an uppercase ISO 3166-1 alpha-2 country code (e.g. "HR", "CZ"), or null. The optional `hullType` is 'monohull', 'catamaran' or 'trimaran', or null when unknown. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ship_write Change boats ~134
Create, update or delete one of the caller's boats. The optional `flag` field is a ship's flag state as an uppercase ISO 3166-1 alpha-2 country code (e.g. "HR", "CZ"), or null. The optional `hullType` is 'monohull', 'catamaran' or 'trimaran', or null when unknown. Sending null for `flag` or `hullType` clears it. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stats Logbook statistics ~279
The caller's lifetime logbook statistics across their whole log — the trips they own AND the trips shared with them as linked crew. Returns totals (distance in meters, moving/total time in seconds, days at sea, distinct shipmates, best sustained 1/5/10-minute speeds in knots, average speed, earliest trip date), a per-year breakdown (by trip start-date year, newest first), and a per-boat breakdown (own and shared boats, each flagged `owned`; by distance, largest first). The optional `role` filters every figure by the role the caller held on each trip: 'all' (default) counts every voyage, 'skipper' or 'crew' count only voyages where the caller held that role. Voyages where the caller is not on the crew have no role: they count only under 'all' and are reported as `unattributedTripsCount`. `ownedTripsCount` and `sharedTripsCount` split the whole log into voyages the caller owns and voyages shared with them, whatever the `role`. All distances are meters and all durations seconds — never nmi/hours; speeds are knots or null. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| role | – | – | – |
No output schema declared.
No examples provided.
track_read Read tracks ~105
Read a leg's GPX track: get the current track, and audit every kept/dropped point with its drop reason. Audit results are paged with offset/limit; a long track has many points. On a trip someone else shared with the caller, `get` reads the track; the audit stays the owner's. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
track_write Change tracks ~222
Change a leg's GPX track: import raw GPX text (inline, capped at 5 Mi UTF-16 code units — that is what the schema counts, so it is roughly 5 MB for plain-ASCII GPX and no less for a file full of non-ASCII names; the server-side pipeline caps are separate: 32 MB of bytes AND at most 75,000 trackpoints per file — a file over the inline cap goes through the REST upload route instead, and one over the point cap has to be split or simplified first), reprocess the leg's stored raw file at the current pipeline version, and delete the track (the leg reverts to statsSource 'manual', retaining its last computed stats). A file whose timed points span more than 60 days is refused on import and reprocess with leg_too_long (422), as no leg may be that long. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trip_read Read trips ~239
Read the caller's voyages: list (the caller's OWN log), list the trips others shared with the caller (list_shared), get one trip, get its combined map, and get its public share link (get_share). `get` composes trip metadata with its crew, charter, legs and diary (there is no separate crew or charter read; the diary also has diary_read). `map` returns a GeoJSON FeatureCollection with one feature per mappable leg — track-backed, or manual with both endpoints set; a leg with no geometry is omitted. A trip someone else shared with the caller is readable with `get` and `map` and listed by `list_shared`, never by `list`; its charter is withheld, and so is the `pickupBase` summary field. `get_share` returns the trip's public, read-only, no-login link or null. Charter price/deposit are integer minor units plus an ISO 4217 currency code — never a float. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trip_write Change trips ~394
Change the caller's own voyages: create, update, delete, replace the full crew set (set_crew, PUT semantics), set or clear the charter (set_charter — a null charter clears it), announce the trip to its crew by email (announce), and turn its public link on or off (create_share, revoke_share). A trip spans at most 365 calendar days, first and last included; longer is trip_too_long (422). An update that moves the trip's dates so that a diary entry would fall outside them is refused with diary_outside_trip (409), whose details list those dates; first rewrite those entries on days inside the new dates and delete them (diary_write), or pick dates that keep them. Charter price/deposit are integer minor units plus an ISO 4217 currency code — never a float. Inviting a crew member to the app is person_write's `invite`/`accept_invitation`: an invitation is person-scoped, and accepting one shares every trip of that owner whose crew that person is on, past and future. `announce` mails the trip's particulars to crew who have a linked account and have not switched that category off in Settings; it reports how many actually went out, and is rate-limited per trip and per recipient address. `create_share` turns on a public, read-only, no-login link to one of the caller's OWN trips and returns its URL (idempotent — one link per trip, calling it again returns the same URL); `revoke_share` turns it off. The public view is redacted — no charter, crew shown as initials only, no owner details — but anyone with the link can open it, so the URL is semi-public. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whoami Current user ~59
The authenticated caller's own profile (id, email, name, language). Takes no arguments. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Seamark MCP server?
Seamark is a hosted endpoint at https://seamark.app/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 · seamark.app
claude mcp add --transport http app-seamark-seamark 'https://seamark.app/mcp'
What is the Seamark MCP server?
Seamark is an MCP server listed in the public MCP registry as app.seamark/seamark. Personal sailing voyage log: trips, legs, ships, crew and GPX tracks with honest statistics. This page covers its hosted endpoint (https://seamark.app/mcp).
Is the Seamark MCP server safe to use?
Seamark scores 88 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 Seamark MCP server expose?
Seamark exposes 15 tools: whoami, trip_read, trip_write, ship_read, ship_write, and 10 more. Their descriptions and schemas cost roughly 3,754 tokens of context every time the server is loaded.
Does the Seamark MCP server require authentication?
Yes. Seamark asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Seamark MCP server still maintained?
Seamark is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Seamark MCP server?
VerifyMCP ran 13 checks on Seamark, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.