Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cosmic's Coast Map

REMOTE · COAST.COSMICOTTER.CA

Tides, currents, marine forecasts and warnings for paddlers, anglers and small boats, 26 countries.

+3 this week 79 Trust /100

Last scanned (4 minutes ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1528 tokens (~138/item across 11 items; 11 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 Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 4 Nov 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.

  • 2 Nov 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.

  • 31 Oct 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.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Probed https://coast.cosmicotter.ca/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.cosmicotter.ca CN=YR2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 RSA 2048 SHA256-RSA 645fa7f3fa400edce23b30ae5f1f6e34a7a
SANs: *.cosmicotter.ca, cosmicotter.ca
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of coast.cosmicotter.ca. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ca. present 26384 13 Verified
cosmicotter.ca. 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=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://coast.cosmicotter.ca/mcp Verified 200
http (plaintext) http://coast.cosmicotter.ca/mcp HTTPS enforced 308 https://coast.cosmicotter.ca/mcp
MCP tools · 11 exposed · ~1,214 tokens

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 →

Tool Tokens
best_low_tides ~128

The lowest daylight low tides over the next days (default 30, up to 90 with a pass key), marking the good ones for clamming, foraging and tide pools.

NameTypeReqDescription
daysinteger––
latnumber–Latitude in decimal degrees (WGS84).
lngnumber–Longitude in decimal degrees (WGS84), negative west of Greenwich.
stationstring–Station code from find_stations (e.g. "07795" for Victoria Harbour, "9447130" for Seattle). Give this or lat/lng.

No output schema declared.

No examples provided.

coast_map_pass ~75

What the Coast Map Pass adds over the free map (offline regions for trips with no signal; longer tide and current ranges for assistants), its prices (CA$5 a month or CA$55 a year), whether it is on sale yet, and the purchase or support links. Covers offline use, longer tide ranges and upgrading.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

currents ~184

Slack water and maximum flood/ebb times and speeds at a current station, in local time. Up to 7 days free; longer with a Coast Map Pass key.

NameTypeReqDescription
daysinteger–Days to cover, starting today at the station (default 2). Up to 7 free; up to 90 with a Coast Map Pass key.
fromstring–First day as YYYY-MM-DD in the station's time zone (default today). Free keys reach 7 days ahead of today.
latnumber–Latitude in decimal degrees (WGS84).
lngnumber–Longitude in decimal degrees (WGS84), negative west of Greenwich.
stationstring–Station code from find_stations (e.g. "07795" for Victoria Harbour, "9447130" for Seattle). Give this or lat/lng.

No output schema declared.

No examples provided.

find_stations ~119

Nearest tide stations (high/low times) and current stations (slack water, max flood/ebb) to a point, with distance and time zone. Coverage: Canada, the US, Norway, Ireland, the Netherlands, New Zealand, Australia (Queensland) and modelled tides elsewhere.

NameTypeReqDescription
kindstring––
latnumberyesLatitude in decimal degrees (WGS84).
limitinteger––
lngnumberyesLongitude in decimal degrees (WGS84), negative west of Greenwich.

No output schema declared.

No examples provided.

marine_forecast ~97

Hourly wind and gusts (knots), direction, temperature, rain, fog and thunder risk for the next 48 hours, plus wave height and period, from Environment Canada (HRDPS/GDWPS), the US National Weather Service or MET Norway.

NameTypeReqDescription
latnumberyesLatitude in decimal degrees (WGS84).
lngnumberyesLongitude in decimal degrees (WGS84), negative west of Greenwich.

No output schema declared.

No examples provided.

marine_warnings ~66

Marine warnings (gale, storm, small craft…) in effect for the marine forecast area at a point.

NameTypeReqDescription
latnumberyesLatitude in decimal degrees (WGS84).
lngnumberyesLongitude in decimal degrees (WGS84), negative west of Greenwich.

No output schema declared.

No examples provided.

pass_status ~80

Checks whether the payment for a purchase reference has completed. Returns pending (with a retry interval) or paid with the pass key, which is sent as "Authorization: Bearer <key>" from then on, plus a link that activates the pass in the user's own map.

NameTypeReqDescription
referencestringyesThe reference from start_pass_purchase (ag_…).

No output schema declared.

No examples provided.

plan_paddle ~144

One call that answers "what will the water be like at this spot?": the nearest tide station with 2 days of highs and lows, currents nearby, the next 24 h of wind, gusts and waves with the maxima, warnings in effect, water temperature and sunrise/sunset, with the important heads_up lines listed first.

NameTypeReqDescription
fromstring–First day as YYYY-MM-DD in the station's time zone (default today). Free keys reach 7 days ahead of today.
latnumberyesLatitude in decimal degrees (WGS84).
lngnumberyesLongitude in decimal degrees (WGS84), negative west of Greenwich.

No output schema declared.

No examples provided.

start_pass_purchase ~71

Begin a Coast Map Pass purchase without leaving the conversation: returns checkout links (CA$5 a month or CA$55 a year, Stripe, no account) tagged with a purchase reference, or says the pass is not on sale yet. The user pays in their browser; the reference identifies that payment afterwards.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tide_times ~190

High and low tides with heights, in the station's local time. Up to 7 days ahead free; longer ranges (up to 90 days) need the user's Coast Map Pass key.

NameTypeReqDescription
daysinteger–Days to cover, starting today at the station (default 2). Up to 7 free; up to 90 with a Coast Map Pass key.
fromstring–First day as YYYY-MM-DD in the station's time zone (default today). Free keys reach 7 days ahead of today.
latnumber–Latitude in decimal degrees (WGS84).
lngnumber–Longitude in decimal degrees (WGS84), negative west of Greenwich.
stationstring–Station code from find_stations (e.g. "07795" for Victoria Harbour, "9447130" for Seattle). Give this or lat/lng.

No output schema declared.

No examples provided.

water_temperature ~60

Water temperature from the nearest buoy within 40 km, otherwise satellite sea surface temperature.

NameTypeReqDescription
latnumberyesLatitude in decimal degrees (WGS84).
lngnumberyesLongitude in decimal degrees (WGS84), negative west of Greenwich.

No output schema declared.

No examples provided.

Install

How do I install the Cosmic's Coast Map MCP server?

Cosmic's Coast Map is a hosted endpoint at https://coast.cosmicotter.ca/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 · coast.cosmicotter.ca

# add to Claude Code
claude mcp add --transport http brendoncampbell-coast-map 'https://coast.cosmicotter.ca/mcp'
Common questions

What is the Cosmic's Coast Map MCP server?

Cosmic's Coast Map is an MCP server listed in the public MCP registry as io.github.brendoncampbell/coast-map. Tides, currents, marine forecasts and warnings for paddlers, anglers and small boats, 26 countries. This page covers its hosted endpoint (https://coast.cosmicotter.ca/mcp).

Is the Cosmic's Coast Map MCP server safe to use?

Cosmic's Coast Map scores 79 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 Cosmic's Coast Map MCP server expose?

Cosmic's Coast Map exposes 11 tools: find_stations, plan_paddle, tide_times, currents, best_low_tides, and 6 more. Their descriptions and schemas cost roughly 1,214 tokens of context every time the server is loaded.

Does the Cosmic's Coast Map MCP server require authentication?

No. We connected to Cosmic's Coast Map without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Cosmic's Coast Map MCP server still maintained?

Cosmic's Coast Map is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.