Remote MCP · Endpoint

Loqal MCP server

No. Loqal answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
br.com.loqal/loqal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
108 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Profissionais de serviços locais no Brasil: encanador, eletricista, diarista e +270 tipos
Website
https://loqal.com.br/para-agentes
Listing
From the official MCP registry (active).
Recent checks of Loqal
CheckedResultHandshake
1 hour agoHandshake completed108 ms
2 days agoHandshake completed120 ms
4 days agoHandshake completed123 ms
6 days agoHandshake completed192 ms
8 days agoHandshake completed294 ms
10 days agoHandshake completed64 ms
12 days agoHandshake completed82 ms
14 days agoHandshake completed54 ms
16 days agoHandshake completed225 ms
17 days agoHandshake completed140 ms
18 days agoHandshake completed125 ms
20 days agoHandshake completed75 ms
22 days agoHandshake completed74 ms
24 days agoHandshake completed161 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.

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