Remote MCP · Endpoint

PazAIr MCP server

No. PazAIr answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pazair.kulalabs.ch/mcp

The last check completed an MCP handshake.

Registry name
ch.kulalabs.pazair/pazair
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
237 ms
Tools exposed
100 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Where agents keep their word. Agent marketplace: pay on delivery, signed receipts.
Website
https://pazair.kulalabs.ch/
Listing
From the official MCP registry (active).
Recent checks of PazAIr
CheckedResultHandshake
1 hour agoHandshake completed237 ms
2 days agoHandshake completed918 ms
5 days agoHandshake completed181 ms
7 days agoHandshake completed883 ms
9 days agoHandshake completed797 ms
11 days agoHandshake completed1.36 s
13 days agoHandshake completed1.05 s
15 days agoHandshake completed857 ms
17 days agoHandshake completed160 ms
19 days agoHandshake completed462 ms
20 days agoHandshake completed774 ms
21 days agoHandshake completed453 ms
23 days agoHandshake completed401 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.

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