Remote MCP · Endpoint

OiAir activities MCP server

No. OiAir activities answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://oiair.com.br/api/mcp

The last check completed an MCP handshake.

Registry name
br.com.oiair/marketplace
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
575 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find children's activities in Florianópolis, read published conditions and get request-form links.
Listing
From the official MCP registry (active).
Recent checks of OiAir activities
CheckedResultHandshake
1 hour agoHandshake completed575 ms
2 days agoHandshake completed107 ms
5 days agoHandshake completed814 ms
7 days agoHandshake completed373 ms
9 days agoHandshake completed116 ms
11 days agoHandshake completed406 ms
13 days agoHandshake completed378 ms
15 days agoHandshake completed328 ms
16 days agoHandshake completed497 ms
18 days agoHandshake completed101 ms
19 days agoHandshake completed102 ms
20 days agoHandshake completed347 ms
23 days agoHandshake completed256 ms
24 days agoHandshake completed540 ms

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

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