Seamark MCP server
app.seamark/seamarkseamark.appstreamable-httpv1.6.0Scanned
Personal sailing voyage log: trips, legs, ships, crew and GPX tracks with honest statistics.
13 tools: 5 can delete or cancel things, 1 do something that can't be undone, 1 change things and 6 only read.
- Reads private data · 2
- Reads text others write · 1
- Can send data out · 1
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Seamark MCP server can do
The Seamark MCP server is published by seamark.app, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (5 tools: trip_write, ship_write, person_write, leg_write and 1 more), do things that cannot be undone, such as sending, paying or publishing (resume) and create or change data (1 tool: stats). 6 tools only read.
2 tools read private data (whoami and person_read); 1 tool brings in text other people can write (whoami); 1 tool can send data out of your system (resume). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 3 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Deletes or cancels 5Claude Code: deny
leg_writeChange 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).1 finding
Why it is in this group
- The name "leg_write" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Findings
- Info
The description is 2,151 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds."
Description, as the server wrote it 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. 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. A later hand-edit of either WIND field flips weatherSource back to 'manual' and clears weatherFetchedAt; writing seaState does NOT, because the pair records where the wind came from and sea state is never fetched. A leg with no usable coordinates or no usable time window is weather_no_position (422); an upstream failure or a date the provider does not cover is weather_unavailable (503). IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Annotations the server declares
- title: Change legs
- destructiveHint: true
person_writeChange the caller's private address book of people — crew and contacts (create, update, delete, unlink_account, mark_self, unmark_self, invite, accept_invitation).1 finding
Why it is in this group
- The name "person_write" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Findings
- Info
The description is 2,236 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds."
Description, as the server wrote it 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 `linkedAccount`/invitations — "this is me" is the caller's own identity, not an access grant. IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Annotations the server declares
- title: Change people
- destructiveHint: true
ship_writeCreate, update or delete one of the caller's boats.No findings
Why it is in this group
- The name "ship_write" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Change boats
- destructiveHint: true
track_writeChange 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 …No findings
Why it is in this group
- The name "track_write" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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 (#191) — 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). IDs are 6-character case-sensitive alphanumeric strings. Timestamps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds.
Annotations the server declares
- title: Change tracks
- destructiveHint: true
trip_writeChange 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), ann…No findings
Why it is in this group
- The name "trip_write" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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). 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.
Annotations the server declares
- title: Change trips
- destructiveHint: true
Can't be undone 1Claude Code: ask
resumeThe 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 star…Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "resume" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- title: Sailing résumé
- readOnlyHint: true
Changes things 1Claude Code: ask
statsThe caller's lifetime logbook statistics across their whole log — the trips they own AND the trips shared with them as linked crew.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Logbook statistics
- readOnlyHint: true
Only reads 6Show 6 read-only tools
leg_readRead a trip's ordered legs: list them, or get one by id.No findings
Why it is in this group
- The name "leg_read" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read legs
- readOnlyHint: true
person_readRead the caller's private address book of people — crew and contacts: list them all, or get one by id.Reads private dataNo findings
Why it is in this group
- The name "person_read" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "contact": it reads contacts.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read people
- readOnlyHint: true
ship_readRead the caller's boats — a reusable, per-owner registry: list them all, or get one by id.No findings
Why it is in this group
- The name "ship_read" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read boats
- readOnlyHint: true
track_readRead a leg's GPX track: get the current track, and audit every kept/dropped point with its drop reason.No findings
Why it is in this group
- The name "track_read" says "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read tracks
- readOnlyHint: true
trip_readRead 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 lin…No findings
Why it is in this group
- The name "trip_read" says "read": a word for reading.
Description, as the server wrote it 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, and legs (there is no separate crew or charter 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.
Annotations the server declares
- title: Read trips
- readOnlyHint: true
whoamiThe authenticated caller's own profile (id, email, name, language).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "whoami" says "whoami": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Current user
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__seamark__resume"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:30 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://seamark.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://seamark.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (6 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://seamark.app/mcp: tools/list returned 15 tools to an anonymous client, including trip_write (destructive), ship_write (destructive), person_write (destructive), leg_write (destructive), diary_write (destructive) and 3 more
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 7 to 8
Findings
Matches of fixed checks, with the text they matched.
- Warnresume
The server marks "resume" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
- Infoperson_write
The description is 2,236 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds."
- Infoleg_write
The description is 2,151 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ps are UTC ISO 8601. Distances are integer meters. Durations are integer seconds."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
- Tools that change things, listed without credentials: 7 to 8
Install
Pinned to version 1.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http seamark https://seamark.app/mcpclaude mcp add --transport http seamark https://seamark.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__seamark__whoami",
"mcp__seamark__trip_read",
"mcp__seamark__ship_read",
"mcp__seamark__person_read",
"mcp__seamark__leg_read",
"mcp__seamark__track_read"
],
"ask": [
"mcp__seamark__stats",
"mcp__seamark__resume"
],
"deny": [
"mcp__seamark__trip_write",
"mcp__seamark__ship_write",
"mcp__seamark__person_write",
"mcp__seamark__leg_write",
"mcp__seamark__track_write"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as seamark. Review it before you use it.
Capability tags behind 3 rules
- mcp__seamark__whoami private-data, untrusted-input
- mcp__seamark__person_read private-data
- mcp__seamark__resume outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.seamark/seamark/verify?hash=177671541ac5b6ef04ad4e8a4e83636efa6d3b394c1e6b6d85a9166fca20eb15" | jq -e '.changed == false'Pinned hash 177671541ac5, from Nov 10, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.seamark/seamark/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.seamark/seamark)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:45 UTC.
Seamark MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Seamark MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 7 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Seamark MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: trip_write, ship_write, person_write, leg_write and track_write.
Can the Seamark MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: resume.
What tools does the Seamark MCP server have?
- 13 tools: 5 destructive, 1 irreversible, 1 write, 6 read. trip_write, ship_write, person_write, leg_write, track_write, resume, stats, whoami and 5 more.
Does the Seamark MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Seamark MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): resume.
Has the Seamark MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.