Remote MCP · Endpoint

dev.passagens/passagens-api MCP server

No. dev.passagens/passagens-api answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://passagens.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.passagens/passagens-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Brazil-first flight price search for AI agents: Portuguese place names, BRL, disclosed affiliate
Listing
From the official MCP registry (active).
Recent checks of dev.passagens/passagens-api
CheckedResultHandshake
1 hour agoHandshake completed87 ms
1 day agoHandshake completed146 ms
2 days agoHandshake completed172 ms
3 days agoHandshake completed172 ms
4 days agoHandshake completed198 ms
5 days agoHandshake completed90 ms
6 days agoHandshake completed206 ms
9 days agoHandshake completed3.94 s
12 days agoHandshake completed268 ms
14 days agoHandshake completed304 ms
16 days agoHandshake completed145 ms
18 days agoHandshake completed105 ms
20 days agoHandshake completed152 ms
22 days agoHandshake completed113 ms
24 days agoHandshake completed83 ms
26 days agoHandshake completed132 ms
27 days agoHandshake completed137 ms
28 days agoHandshake completed330 ms

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

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