_ registry / mcp streamable-http · checked 3h ago

globalsurfari

https://globalsurfari.com

Registry code: c1a6e06c438797a1

api record

Open surf forecast server - no authentication required. Use get_surf_forecast with coordinates, or get_surf_forecast_by_spot with a beach name. Forecasts are 7 days from NOAA wave model data; heights in feet, wind in mph.

endpoint
https://globalsurfari.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is globalsurfari live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is globalsurfari free to use?
Not anonymously — it refuses callers without credentials. The hub cannot see whether credentials cost anything.
What tools does globalsurfari have?
3 tools: get_surf_forecast_by_spot, get_surf_forecast, list_surf_spots.
Is globalsurfari safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.7%

90 days 99.2%· all time 99.2%

latency
1,520ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 471 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
weather & environment forecast
used for
  • get a 7-day surf forecast for coordinates
  • get a surf forecast for a named spot
  • list saved surf spots
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_surf_spots reads open 34d ago

    Lists surf spots saved by Global Surfari users (popular and recently added).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_surf_forecast_by_spot reads unknown 34d ago

    7 day surf forecast for a named surf spot. Tries saved Global Surfari locations first, then geocodes the name. Example: "Bondi Beach", "Mavericks", "Bells Beach".

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Surf spot or beach name"
    }
  }
}
    arguments 12 lines
  • get_surf_forecast reads unknown 34d ago

    7 day surf forecast (wave height in feet, wave period in seconds, wind speed in mph, wind direction in degrees) for the nearest coastal forecast point to a latitude/longitude. Data from NOAA wave models.

    mcp-tool

    {
  "type": "object",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "latitude": {
      "type": "number",
      "description": "Latitude in decimal degrees (-90 to 90)"
    },
    "longitude": {
      "type": "number",
      "description": "Longitude in decimal degrees (-180 to 180)"
    }
  }
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c1a6e06c438797a1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c1a6e06c438797a1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c1a6e06c438797a1/badge.svg)](https://brick.blue/agent/c1a6e06c438797a1?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.