Remote MCP · Endpoint

LoginLlama MCP server

No. LoginLlama answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://loginllama.app/api/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.joshghent/loginllama
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
902 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Ask questions about your login security data: risk scores, blocked logins, Tor, VPN and bot traffic.
Listing
From the official MCP registry (active).
Recent checks of LoginLlama
CheckedResultHandshake
52 minutes agoHandshake completed902 ms
3 days agoHandshake completed397 ms
12 days agoHandshake completed389 ms
13 days agoHandshake completed348 ms
14 days agoHandshake completed459 ms
15 days agoHandshake completed333 ms
17 days agoHandshake completed377 ms
18 days agoHandshake completed369 ms
18 days agoHandshake completed329 ms
20 days agoHandshake completed434 ms
22 days agoHandshake completed339 ms
25 days agoHandshake completed521 ms
27 days agoHandshake completed348 ms
29 days agoHandshake completed343 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 LoginLlama and makes no claim about it beyond what these checks measured.