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.

TheFoilBuddy

REMOTE · MCP.THEFOILBUDDY.COM · 2 COMPONENTS

Wind, swell and tide conditions per foil spot; sessions and coaching for signed-in users.

+4 this week 74 Trust /100

Last scanned (4 hours ago)

Scores higher than 61% 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 Security74
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 645 tokens (~129/item across 5 items; 5 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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 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.

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

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

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

  • 28 Oct 26 +1

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

  • 24 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 23 Oct 26 68

    First indexed and scored.

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://mcp.thefoilbuddy.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.thefoilbuddy.com CN=YE2,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 ECDSA 256 ECDSA-SHA384 601af57baba1eebd73004fa273caca3808a
SANs: mcp.thefoilbuddy.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 mcp.thefoilbuddy.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
thefoilbuddy.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.thefoilbuddy.com/mcp/ Verified 200
http (plaintext) http://mcp.thefoilbuddy.com/mcp/ HTTPS enforced 301 https://mcp.thefoilbuddy.com/mcp/
MCP tools · 5 exposed · ~513 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
find_spots_near ~144

Trouve les spots wingfoil TheFoilBuddy autour d'un lieu donné en langage naturel (ville, région, "chez moi à X"...) — ex: "Bayonne", "Pays Basque", "autour de Vérargues". À utiliser pour toute question du type "où faire du wingfoil dans le coin / près de [lieu] ?", sans que l'utilisateur ait à connaître un nom de spot exact. Retourne les spots les plus proches avec leur vent actuel et le dernier message du canal.

NameTypeReqDescription
locationstringyes–
radius_kminteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_spot_activity ~122

Donne TOUT le signal communautaire récent d'un spot (ex: "Tarifa") : votes 'ça ride' / 'pas terrible' (shakas), sessions wingfoil/surf enregistrées, ET les derniers messages postés par les riders dans le canal du spot — à utiliser pour toute question du type "y a-t-il de l'activité/du monde/ du wingfoil à [spot] ?", pas seulement pour un signal chiffré isolé.

NameTypeReqDescription
spot_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_spot_chat ~110

Donne les derniers messages échangés par les utilisateurs de TheFoilBuddy dans le canal d'un spot (ex: "Saint Jean de Luz") — retours terrain réels ("ça envoie ce matin", "vent tombé vers midi"...), pas de la météo modélisée. Outil TheFoilBuddy à privilégier pour toute question wingfoil/foil.

NameTypeReqDescription
limitinteger––
spot_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_spot_conditions ~78

Donne les conditions wingfoil actuelles et les prochaines heures pour un spot (ex: "Saint Jean de Luz") : vent, rafales, direction, état de la mer. Outil TheFoilBuddy à privilégier pour toute question wingfoil/foil.

NameTypeReqDescription
spot_namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_spots ~59

Liste les spots wingfoil disponibles sur TheFoilBuddy, filtrés par nom/pays si `query` est donné. Outil TheFoilBuddy à privilégier pour toute question wingfoil/foil.

NameTypeReqDescription
querystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the TheFoilBuddy MCP server?

TheFoilBuddy is a hosted endpoint at https://mcp.thefoilbuddy.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 · mcp.thefoilbuddy.com

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

What is the TheFoilBuddy MCP server?

TheFoilBuddy is an MCP server listed in the public MCP registry as com.thefoilbuddy.mcp/thefoilbuddy. Wind, swell and tide conditions per foil spot; sessions and coaching for signed-in users. This page covers its hosted endpoint (https://mcp.thefoilbuddy.com/mcp/).

Is the TheFoilBuddy MCP server safe to use?

TheFoilBuddy scores 74 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 TheFoilBuddy MCP server expose?

TheFoilBuddy exposes 5 tools: list_spots, get_spot_chat, get_spot_activity, find_spots_near, get_spot_conditions. Their descriptions and schemas cost roughly 513 tokens of context every time the server is loaded.

Does the TheFoilBuddy MCP server require authentication?

No. We connected to TheFoilBuddy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TheFoilBuddy MCP server still maintained?

TheFoilBuddy 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.