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.

World Beach Map: beaches and sea temperature

REMOTE · BEACHMAPWORLD.COM

Beaches worldwide from Wikidata, each with twelve monthly NOAA sea temperatures. No key.

+3 this week 75 Trust /100

Last scanned (4 hours ago)

Scores higher than 64% 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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 637 tokens (~159/item across 4 items; 4 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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 5 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.

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

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

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 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.

  • 23 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.

  • 22 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
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://beachmapworld.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=beachmapworld.com CN=WE1,O=Google Trust Services,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA256 36aecb9fb17402190e3aa3846366cb27
SANs: beachmapworld.com, *.beachmapworld.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of beachmapworld.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
beachmapworld.com. present 2371 13 Verified
beachmapworld.com. Verified address RRset verified with the apex keys
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=15552000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=(), usb=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://beachmapworld.com/mcp Verified 200
http (plaintext) http://beachmapworld.com/mcp HTTPS enforced 301 https://beachmapworld.com/mcp
MCP tools · 4 exposed · ~432 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
get_beach ~69

Full profile of one beach by id (its slug, from search results), by Wikidata Q-id, or by name.

NameTypeReqDescription
id_or_namestringyesBeach id (e.g. "navagio"), Wikidata Q-id (e.g. "Q2460851") or name

No output schema declared.

No examples provided.

sea_temperature_year ~55

The twelve monthly means for one beach, plus the months that reach 20 °C. Answers "when is it warm enough there?".

NameTypeReqDescription
id_or_namestringyesBeach id, Wikidata Q-id or name

No output schema declared.

No examples provided.

search_beaches ~177

Search and filter the atlas. All filters optional and combinable. Returns compact records; use get_beach for a full profile.

NameTypeReqDescription
countrystring–ISO-2 code or country name (e.g. "PT" or "Portugal")
limitinteger–Max results, default 10, max 50
min_sea_temp_cnumber–Minimum mean sea temperature in that month, or of the warmest month when no month is given
monthstring|number–Rank and report the sea temperature for this month (name or 1-12)
querystring–Free-text match on beach name, region or country
shore_typestring–Shore type, from the beach own Wikidata classes. "beach" means Wikidata does not say.

No output schema declared.

No examples provided.

warmest_beaches_in_month ~131

Beaches ranked by their MEAN sea temperature in one month, warmest first. This is the question the atlas exists to answer: "where can I swim in February?". Beaches with no measurement are excluded rather than ranked as cold.

NameTypeReqDescription
countrystring–ISO-2 code or country name
limitinteger–Max results, default 15, max 50
min_sea_temp_cnumber–Only beaches at or above this monthly mean, e.g. 20
monthstring|numberyesMonth name or number 1-12

No output schema declared.

No examples provided.

Install

How do I install the World Beach Map: beaches and sea temperature MCP server?

World Beach Map: beaches and sea temperature is a hosted endpoint at https://beachmapworld.com/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 · beachmapworld.com

# add to Claude Code
claude mcp add --transport http com-europebeachmap-beachmap 'https://beachmapworld.com/mcp'
Common questions

What is the World Beach Map: beaches and sea temperature MCP server?

World Beach Map: beaches and sea temperature is an MCP server listed in the public MCP registry as com.europebeachmap/beachmap. Beaches worldwide from Wikidata, each with twelve monthly NOAA sea temperatures. No key. This page covers its hosted endpoint (https://beachmapworld.com/mcp).

Is the World Beach Map: beaches and sea temperature MCP server safe to use?

World Beach Map: beaches and sea temperature scores 75 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 World Beach Map: beaches and sea temperature MCP server expose?

World Beach Map: beaches and sea temperature exposes 4 tools: search_beaches, get_beach, warmest_beaches_in_month, sea_temperature_year. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

Does the World Beach Map: beaches and sea temperature MCP server require authentication?

No. We connected to World Beach Map: beaches and sea temperature without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the World Beach Map: beaches and sea temperature MCP server still maintained?

World Beach Map: beaches and sea temperature 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.