Remote MCP · Endpoint

My Noticeboard MCP server

No. My Noticeboard answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://mynoticeboard.org.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.org.mynoticeboard/directory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
397 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Local support, community groups and what's on along the Jurassic Coast (Dorset and East Devon).
Listing
From the official MCP registry (active).
Recent checks of My Noticeboard
CheckedResultHandshake
36 minutes agoHandshake completed397 ms
3 days agoHandshake completed311 ms
13 days agoHandshake completed334 ms
14 days agoHandshake completed229 ms
15 days agoHandshake completed129 ms
16 days agoHandshake completed123 ms
17 days agoHandshake completed264 ms
18 days agoHandshake completed145 ms
19 days agoHandshake completed142 ms
20 days agoHandshake completed357 ms
22 days agoHandshake completed401 ms
25 days agoHandshake completed359 ms

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

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 My Noticeboard and makes no claim about it beyond what these checks measured.