LoginLlama MCP Server

by joshghent Your server? Claim it

answering

LoginLlama is answering right now. Last checked 11 min ago. It exposes 5 tools.

Ask questions about your login security data: risk scores, blocked logins, Tor, VPN and bot traffic.

Uptime history 23 days of history

23 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

311 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check LoginLlama every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add loginllama --transport http https://loginllama.app/api/v1/mcp

Settings → Connectors → Add custom connector, then paste this address

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

~/.codex/config.toml

[mcp_servers.loginllama]
url = "https://loginllama.app/api/v1/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "loginllama": {
      "url": "https://loginllama.app/api/v1/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "loginllama": {
      "type": "http",
      "url": "https://loginllama.app/api/v1/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

get_login_breakdown

Group logins by a dimension (browser, os, device, country, or status) and return counts, average risk score and high-risk counts per group. Good for "which browser has the highest risk".

get_login_stats

Overall login security summary for your team: total checks, average risk score, high-risk count, blocked/failed logins, and bot/Tor/VPN counts. Supports filtering by browser, OS, country, device, user and time window.

account

get_account_usage

Your LoginLlama account usage: remaining API credits for production and staging, and plan name.

average

get_average_risk_score

Average login risk score (0-10) across matching logins. Use the filters to answer questions like "what is my average login risk score for the chrome browser".

recent

get_recent_logins

List the most recent login checks (newest first) with risk score, status, location and device. Supports the same filters.

Endpoints

URL	Transport	State	Latency	Checked
https://loginllama.app/api/v1/mcp	streamable-http	answering	243 ms	11 min ago

Alternatives to LoginLlama

same job, measured the same way

Kodem

by kodemsecurity

Ask about your Kodem Security data and act on findings in plain language, with your permissions.

answering

ResponseHub

by responsehub

Answer security questionnaires and RFPs from your AI knowledge base.

answering

Contract Scanner

by lordbasilaiassistant-sudo

Smart contract security scanner — vulnerabilities, risk scores, and calldata decoding

49 installs/wk local only

Scout Security

by varpost

Deterministic, zero-token security scanner your AI agent calls to find and re-verify issues.

208 installs/wk local only

RFP.ai

by rfp

Draft cited RFP and security questionnaire answers from your knowledge base, with human review

answering

COLA Insight

by ge3m0r

Read-only Social Security COLA data, calculations, history, and official source links.

5 tools answering

Eleion Scanner

by hernaninverso

55 installs/wk local only

mcpm

by getmcpm

MCP security guard + package manager: trust-scored installs, blocks prompt injection and rug-pulls.

2 130 installs/wk local only

LoginLlama — questions

Answers built from our own checks of this server.

What can LoginLlama do?

It exposes 5 tools, read directly from the server on our last check. Among them: get_account_usage, get_average_risk_score, get_login_breakdown, get_login_stats, get_recent_logins. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is LoginLlama working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 311 ms. The bar chart above shows every period we have measured.

How do I connect LoginLlama?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does LoginLlama need an API key?

No. LoginLlama completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is LoginLlama?

It answers our handshake in 311 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.