Remote MCP · Endpoint

BuyingMesh Procurement MCP server

No. BuyingMesh Procurement answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://buyingmesh.com/mcp

The last check completed an MCP handshake.

Registry name
com.buyingmesh/procurement
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
155 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Structured B2B supply search, quoting, sandbox orders and fulfillment status for agents.
Listing
From the official MCP registry (active).
Recent checks of BuyingMesh Procurement
CheckedResultHandshake
1 hour agoHandshake completed155 ms
2 days agoHandshake completed97 ms
5 days agoHandshake completed78 ms
7 days agoHandshake completed129 ms
9 days agoHandshake completed70 ms
11 days agoHandshake completed131 ms
13 days agoHandshake completed120 ms
15 days agoHandshake completed98 ms
17 days agoHandshake completed71 ms
19 days agoHandshake completed57 ms
20 days agoHandshake completed160 ms
21 days agoHandshake completed107 ms
23 days agoHandshake completed80 ms

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

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