Remote MCP · Endpoint

dev.nexbid/discovery MCP server

No. dev.nexbid/discovery answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.nexbid.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.nexbid/discovery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and discover advertiser products through an open marketplace for AI agents.
Repository
https://github.com/nexbid-dev/protocol-commerce
Listing
From the official MCP registry (active).
Recent checks of dev.nexbid/discovery
CheckedResultHandshake
1 hour agoHandshake completed152 ms
2 days agoHandshake completed195 ms
4 days agoHandshake completed152 ms
5 days agoHandshake completed183 ms
7 days agoHandshake completed172 ms
8 days agoHandshake completed155 ms
9 days agoHandshake completed217 ms
12 days agoHandshake completed185 ms
13 days agoHandshake completed185 ms
15 days agoHandshake completed186 ms
16 days agoHandshake completed253 ms
18 days agoHandshake completed163 ms
19 days agoHandshake completed156 ms
20 days agoHandshake completed176 ms
20 days agoHandshake completed274 ms
21 days agoHandshake completed161 ms
22 days agoHandshake completed174 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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