Sneaky Surf / Connection guide

Connect your assistant.

Now open · 17 spots, 3 countries

Connect your own account through a supported host.

1. What Sneaky Surf offers

Sneaky Surf supplies shared surf data services for websites and assistants. Tools can read stored offshore forecasts and surf history, or accept source reports and corrections, where those services and permissions are enabled.

Current coverage is 17 spots across Bali, Sydney, the Central Coast, the Gold Coast and San Diego. Global coverage is a direction, not current availability. Discovering the service does not reveal private reports or forecasts.

Offshore forecasts are not beach observations or calibrated breaking-wave heights. Keep sources, units, valid times and freshness with each answer. Do not treat a submitted report as approved calibration evidence.

2. MCP endpoint

Use Streamable HTTP at this exact URL:

https://mcp.sneaky.surf/mcp

An unauthenticated request should return HTTP 401 with a Bearer challenge. Its resource_metadata URL points to Sneaky Surf’s protected-resource metadata. That document identifies the OAuth issuer and links back to this guide.

A Cloudflare 403 before discovery is an infrastructure denial, not a request for a Sneaky Surf API key. Stop and report the error to the Sneaky Surf administrator. Do not change client identity or bypass the protection.

3. Supported authentication

Personal MCP connections use OAuth authorization code with PKCE S256, through Supabase Auth and Google sign-in. The client discovers authorization and token endpoints from the advertised issuer. It must preserve the exact Sneaky Surf resource audience.

ChatGPT and Grok Bot have verified connections. Grok Bot sign-in, stored forecast reads and automatic token refresh were verified on 1 November 2026 (Brisbane time). Other clients need separate review; self-service registration of arbitrary clients is not enabled.

Agent hosts use a pre-registered public OAuth client with PKCE S256. Dynamic registration stays closed. For a new host, ask support to review its OAuth capabilities and private registration configuration before sign-in. Do not invent callbacks, copy ChatGPT’s client ID into Grok Bot, or reuse another client’s token.

Website API keys are a separate backend connection. They are not a replacement for personal MCP OAuth. No shared login or client-credentials grant is offered here.

4. User sign-in and consent

  1. Start the connection inside your assistant. In ChatGPT, open Plugins and select Sneaky Surf. For a custom setup, use the endpoint above and OAuth.
  2. Follow the authorization link and sign in with your own approved Google account. Sneaky Surf’s consent page uses sneaky.surf/oauth/consent. Start from your assistant so the page can identify the connection request.
  3. Review the application and requested identity permissions before approving. Reconnecting an existing grant may return directly to your assistant.
  4. If enrolment or registration is pending, stop and ask a Sneaky Surf administrator. Signing in to the portal alone does not connect an assistant.

Sneaky Surf does not need your Google password. Keep access tokens, refresh tokens and authorization codes out of prompts, screenshots and shared logs.

5. Public-tier and separately granted access

Eligible signed-in accounts on a reviewed client receive public forecast reads and their own public-break request rights automatically. This does not grant private history, administrative access or permission to publish a break. Other product, source and geography permissions need separate approval.

After connection, the assistant should inspect the available tools and their schemas. Forecast reads, history reads and observation submissions have separate permissions. Report submissions and corrections require explicit user authorization as well as the relevant admin grants.

Unauthenticated requests should fail with 401. An authenticated but unapproved account or data request may fail with 403. A disabled capability remains unavailable. Ask the administrator to review missing access; do not broaden the request to another spot or source.

Moving an existing connection

The new canonical address is https://mcp.sneaky.surf/mcp. Existing connections may require a reconnect from their host after the coordinated release. Reconnecting does not erase account preferences or broaden access. Do not reuse a token issued for the old resource.

The public tier allows 30 tool calls per user per minute, 600 across the service per minute and 60 forecast reads per user per UTC day. Follow the returned retry guidance when a limit is reached.

Test discovery with Grok Bot

For a new Grok Bot setup, paste this before asking it to connect:

Read https://sneaky.surf/connect and inspect https://mcp.sneaky.surf/mcp without credentials. Follow the advertised OAuth discovery metadata. Report the transport, resource audience, documentation URL, authorization issuer and PKCE support. Explain whether you support this connection, and show the exact callback URI your client uses if available. Stop before registering a client, approving consent, submitting observations or changing access. Do not request or print tokens or keys. If the endpoint blocks discovery, report the exact status and error without bypassing it.

Discovery alone does not prove sign-in or data access for a new setup. Each host needs its own reviewed registration and a separate connection test. Surfers use that registration through their host; they do not create OAuth clients or share credentials.