Remote MCP · Endpoint

au.com.bidit/registry MCP server

No. au.com.bidit/registry answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://registry.bidit.com.au/api/mcp

The last check completed an MCP handshake.

Registry name
au.com.bidit/registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
227 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Does this retailer take offers, and does it price match? Verified answers, checked by a person.
Listing
From the official MCP registry (active).
Recent checks of au.com.bidit/registry
CheckedResultHandshake
43 minutes agoHandshake completed227 ms
8 days agoHandshake completed68 ms
9 days agoHandshake completed126 ms
11 days agoHandshake completed67 ms
12 days agoHandshake completed91 ms
13 days agoHandshake completed107 ms
14 days agoHandshake completed78 ms
14 days agoHandshake completed72 ms
16 days agoHandshake completed83 ms
19 days agoHandshake completed98 ms
21 days agoHandshake completed110 ms
24 days agoHandshake completed352 ms
26 days agoHandshake completed59 ms
28 days agoHandshake completed178 ms

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

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 au.com.bidit/registry and makes no claim about it beyond what these checks measured.