Remote MCP · Endpoint

Arugula MCP server

No. Arugula answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.arugulanet.com/mcp?ch=mcp-registry

The last check completed an MCP handshake.

Registry name
com.arugulanet/arugula
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.51 s
Tools exposed
3 tools
Uptime, last 30 days
66.7% from 12 checks
Described by its publisher as
Find offers that fit what you want, ranked by fit only, with links to buy.
Listing
From the official MCP registry (active).
Recent checks of Arugula
CheckedResultHandshake
20 minutes agoHandshake completed1.51 s
3 days agoHandshake completed1.07 s
14 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed1.28 s
18 days agoHandshake completed1.36 s
18 days agoHandshake completed1.33 s
19 days agoHandshake completed1.37 s
21 days agoHandshake completed1.26 s
22 days agoFailed - the request timed out—
25 days agoHandshake completed1.68 s

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 8 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 Arugula and makes no claim about it beyond what these checks measured.

Arugula MCP server - status, uptime and latency - Glide