Remote MCP · Endpoint

Nature's Wild Berry MCP server

No. Nature's Wild Berry answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nwb-mcp.nwb-mcp.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.hankwatt/natureswildberry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
171 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Approved facts, products, prices and where to buy for Nature's Wild Berry miracle berries.
Listing
From the official MCP registry (active).
Recent checks of Nature's Wild Berry
CheckedResultHandshake
1 hour agoHandshake completed171 ms
2 days agoHandshake completed377 ms
4 days agoHandshake completed150 ms
6 days agoHandshake completed150 ms
8 days agoHandshake completed289 ms
10 days agoHandshake completed146 ms
12 days agoHandshake completed154 ms
14 days agoHandshake completed173 ms
15 days agoHandshake completed156 ms
16 days agoHandshake completed386 ms
18 days agoHandshake completed147 ms
20 days agoHandshake completed124 ms
22 days agoHandshake completed81 ms
24 days agoHandshake completed217 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 Nature's Wild Berry and makes no claim about it beyond what these checks measured.