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

surf-session-finder

https://ssf-api-cf.surfsessionfinder.com

Registry code: 0dbbf48224ff430f

api record

Surf park sessions schedule availability and notifications for wave park surfers worldwide

from a public catalogue that lists it, not from the operator

endpoint
https://ssf-api-cf.surfsessionfinder.com/mcp
protocol
streamable-http ·2024-11-05
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 surf-session-finder live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is surf-session-finder free to use?
Yes — the hub reached it with no key and no payment.
What tools does surf-session-finder have?
3 tools: find_sessions, get_session_levels, list_pools.
Is surf-session-finder 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
100%

90 days 100%· all time 100%

latency
114ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 364 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
games & entertainment sports
used for
  • find available surf park sessions
  • list surf pools worldwide
  • get session skill levels for a pool
takes → gives
text, data → 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_pools reads open 20h ago

    List all supported surf pools worldwide with their IDs, names, and locations. Always call this first to get valid pool_id values for the other tools.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • find_sessions reads unknown 20h ago

    Find available surf sessions at a pool. Returns date, time, skill level, available spots, and a booking URL. Filter by level, minimum spots, or time window.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pool_id"
  ],
  "properties": {
    "levels": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filter to specific level names (e.g. [\"Beginner\"]). Omit to return all levels."
    },
    "pool_id": {
      "type": "string",
      "description": "Pool ID — use list_pools to get valid values"
    },
    "min_spots": {
      "type": "number",
      "description": "Minimum available spots required (default: 0)"
    },
    "hours_ahead": {
      "type": "number",
      "description": "Search window in hours from now (default: 192 = 8 days)"
    }
  }
}
    arguments 27 lines
  • get_session_levels reads unknown 20h ago

    Get the available session difficulty levels for a surf pool (e.g. Beginner, Intermediate, Advanced). Use the level names with find_sessions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pool_id"
  ],
  "properties": {
    "pool_id": {
      "type": "string",
      "description": "Pool ID — use list_pools to get valid values"
    }
  }
}
    arguments 12 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 0dbbf48224ff430f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0dbbf48224ff430f/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/0dbbf48224ff430f/badge.svg)](https://brick.blue/agent/0dbbf48224ff430f?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.