Remote MCP · Endpoint

Experience Bamfield MCP server

No. Experience Bamfield answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://experiencebamfield.com/mcp

The last check completed an MCP handshake.

Registry name
com.experiencebamfield/experience-bamfield
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
522 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plan and price trips to Bamfield, BC, and build the guest's cart link. Read-only; no key to connect.
Listing
From the official MCP registry (active).
Recent checks of Experience Bamfield
CheckedResultHandshake
1 hour agoHandshake completed522 ms
11 hours agoHandshake completed324 ms
1 day agoHandshake completed507 ms
2 days agoHandshake completed956 ms
4 days agoHandshake completed726 ms
7 days agoHandshake completed508 ms
9 days agoHandshake completed336 ms
12 days agoHandshake completed535 ms
14 days agoHandshake completed389 ms
16 days agoHandshake completed614 ms
18 days agoHandshake completed348 ms
20 days agoHandshake completed684 ms
22 days agoHandshake completed321 ms
23 days agoHandshake completed290 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Experience Bamfield and makes no claim about it beyond what these checks measured.